Connect tools and agents

Make contracts survive process and protocol boundaries.

Questions to answer

How are schemas, identity, errors, cancellations, and artifacts represented?

Start here

Run the local MCP recipe to compare a direct tool call with a real protocol round trip and explicit failure results.

Begin with tool dispatch in the architecture guide. Consult MCP research and A2A research before adopting a protocol.

Prerequisites: a small task you can describe, its permitted effects, and basic Python for executable examples. Reading the guides needs no API key.

Evidence and coverage

Local Python tool contracts already exist. Remote interoperability examples and tested versions are recorded in the build path; full protocol conformance is not claimed.

Follow the concept and build path for runnable lessons and the ecosystem map for wider coverage. Return to all journeys.