CCAR-F
Tool design and MCP: build clear interfaces
Key takeaways
- Separate the host, client, and server responsibilities.
- Treat a tool schema as an interface, not an authorization system.
- Test missing inputs, unavailable dependencies, and repeated requests.
Understand the interface
MCP’s architecture separates a host application, its clients, and servers exposing capabilities. Tools describe operations with structured inputs. The tool specification defines how tools are discovered and called and how results and errors are represented. Use the current specification when implementing an integration rather than inferring wire behavior from a practice question.
Exercise: design an order lookup tool
Describe an operation that retrieves a synthetic order for a signed-in customer. Write a short purpose statement and a schema containing only inputs the caller should choose. Decide how trusted account identity is supplied outside those inputs. Include result examples for success, a missing record, and an unavailable service.
Compare a broad tool named manage_orders with separate lookup and propose_change operations. Explain which design gives the model a clearer choice and which makes permissions easier for the application to enforce. The appropriate split depends on the workflow; naming alone does not enforce authority.
Test the boundary
Try an empty identifier, an identifier from a different account, an unexpected field, a malformed result, and a timeout. Write the behavior you expect before running the exercise. Check both the model-facing result and the underlying side effect. A reassuring sentence is not evidence that an operation succeeded.
For a synthetic write operation, send the same request twice and simulate a lost acknowledgement. Decide which identifier distinguishes a retry from a new operation, and how the caller can confirm the outcome.
Connect the contract to your agent
Give the agent enough description to choose the operation and interpret the result. Keep sensitive credentials in the application or server configuration. Review whether returned data contains more information than the task needs. Finish by explaining how the tool contract supports the architecture in the agentic architecture guide.
Sources and review
Source links checked 2026-10-10. These exercises are independent CertLabs preparation, not official exam questions or a prediction of passing.
Continue exploring