Skip to content

MCP design reference โ€‹

This is the provided fallback MCP design for Part 5, MCP fundamentals. If you run out of time during the design exercise, adopt this mapping and checklist so you are ready for the Part 6 server build.

Capability mapping โ€‹

CapabilityMCP conceptDescriptionInputsOutputRead-only / approval
Package dataresourceCurrent packages with status, route, and conditionread-only
Route dataresourceRoutes and the packages currently on eachread-only
Data schemaresourceThe shape of package, order, and route recordsread-only
Policy documentresourceShipping and condition rules the agent must respectread-only
Investigate a delayed packagepromptReusable workflow: gather status, route, and recent history for one package
list_packagestoolReturn all package IDs in the systemโ€”package ID listread-only
lookup_packagetoolReturn status, route, condition, and fragile flag for a packagepackage_id: stringformatted package recordread-only
lookup_order_statustoolReturn delivery status and delay details for a packagepackage_id: stringstatus + delay fieldsread-only
lookup_routetoolReturn route details and driver for a route IDroute_id: stringroute recordread-only
update_package_statustoolChange a package's statuspackage_id: string, status: enum{ ok: boolean }approval-required

Design checklist โ€‹

  • At least five capabilities are mapped to an MCP resource, prompt, or tool.
  • Read-oriented context (package data, route data, schema, policy) is mapped to resources, not tools.
  • At least one reusable workflow is mapped to a prompt.
  • At least three tools have named inputs and an expected output.
  • Every operation is marked read-only or approval-required.
  • State-changing operations are marked approval-required for the HITL segment in Part 10.
  • Each description is written for the agent, not a human reader.

Back to Part 5, MCP fundamentals ยท Continue to Part 6, Build the MCP server