Capstone: Stateless Tool Ecosystem
A production agent system is a set of boundaries, not a pile of features. This capstone separates a readable in-process simulation from the protocol clients, authorization server, sandbox, and telemetry exporter a real deployment still needs. Compose tool calls, task-shaped results, delegated work, UI resources, authorization policy, and trace records into one flow. Carry protocol version, client identity, and capabilities on every MCP request instead of relying on a connection session. Discover a server before use and drive long work through the official Tasks extension. Distinguish a protocol-shaped simulation from an MCP, A2A, OAuth, or OpenTelemetry implementation. Map each simulated boundary to the production component that must replace it. Keep AGENTS.md, an Agent Skill, runtime adapters, tools, and security policy in their correct roles. Explain which claims can be verified from local output and which need live integration tests. Design a research-and-report system. A user asks for papers on agent protocols. The system searches a paper catalog, delegates summarization, generates a report, returns a UI resource, and records the path through the system. That sentence hides several independent contracts: a model-facing tool schema;. a stateless request envelope and server discovery contract;. a gateway decision for actor, scope, and tool identity;. a long-running operation contract;. a delegation protocol;. a host-to-app bridge;. trace propagation and export;. a reusable operating procedure. code/main.py keeps…
Capstone: Stateless Tool Ecosystem: A production agent system is a set of boundaries, not a pile of features. This capstone separates a readable in-process…
This free lesson is part of the AI Engineering from Scratch curriculum. Read the full explanation, run the lesson code, and verify the result in the interactive reader or from the repository source.
Browse the complete course catalog or open this lesson on GitHub.