← Back to Concept Contrast

Concept Contrast Fable

Tool registry and Model Context Protocol

Conclusion first:A tool registry is a list that tells you which tools are available. MCP is a set of communication rules that determines how tools are discovered, how they are called, and how results are reported back. A list without rules is like having phone numbers but both sides not speaking the same language.

A tool registry is a list that tells you which tools are available. MCP is a set of communication rules that determines how tools are discovered, how they are called, and how results are reported back. A list without rules is like having phone numbers but both sides not speaking the same language.

Fable

The directory and the telephone line

There was a craftsmen's hall in the city, with a directory on the wall listing who could repair clocks, who could mix medicine, and who could test well water. The new steward only had to look at the directory to know what skills were available in the city.

At first, the directory was very useful. When someone needed a bridge repaired, the steward looked up the carpenter; when someone needed an audit, the steward found the abacus master. But when it came time to actually hire people to work, problems arose: each household submitted orders in different formats—some wanted red paper, some wanted a verbal message, and some only recognized old seals.

The chief steward thought making the directory more detailed would be enough. He added address, price, temperament, and opening hours to each craftsman. The directory became much thicker, but the errand runners were still often sent back, because they did not know which set of rules to follow when handing over materials.

When a well turned muddy, the water tester, mason, and clinic all had to participate. The directory could tell the steward "these people exist in the city," but it could not make the three receive samples, return results, and explain failure reasons in the same way.

The Hundred Crafts Hall later established a unified transmission protocol: whom to invite, what materials to bring, how to state requirements, how the other party should respond, and how to return something when it can't be done—all had a common format. The directory still hung on the wall, but runners no longer had to guess each other's methods.

The new rules also solved the problem of returned requests. In the past, when a master could not do the work, the runner was simply sent back; now it was necessary to explain what materials were missing, which condition was unmet, and whether another master could be substituted. Requests no longer silently disappeared at the door.

Later the Hundred Crafts Hall expanded to neighboring cities, and the directory grew quickly, but the courier route rules stayed consistent. The chief steward no longer had to teach a new set of delivery methods for every new craft. The Hundred Crafts Hall also wrote permissions into the courier route. A clock repairer could receive gear samples but not view medical clinic records; a water inspector could return muddy water samples but not alter bridge blueprints. Unified delivery rules were not just convenient for errands; they also gave every handoff boundaries, receipts, and failure explanations. The chief steward also required a receipt for every call. Who was invited, what they brought, whether the other party accepted it, and what the failure reason was all had to return to the same record.

The old steward kept the two ledgers separate. The thin one answered "what skills are available"; the thick one specified "how to reliably deliver requests and results". The former is like a roster, the latter like a post road; without the post road, knowing who can do the work doesn't guarantee you can actually engage them.

Tool registry

A directory or list recording which external tools an Agent can call, along with each tool's interface description and parameter specifications. It solves the question of 'what is available.'

Model Context Protocol (MCP)

A standardized communication protocol that defines how models and external tools discover, connect, invoke and exchange data. It solves the "how to use it" problem, including authentication, request format, response format and error handling.

Story Mapping

  • Phone book: tool registry, listing the available tools and their descriptions.
  • Every vendor speaks its own language: without a unified protocol, each tool is invoked differently.
  • The unified standard Old Zheng established: what protocols like MCP do—standardizing discovery, invocation and response processes.
  • Availability probe: protocol-level health checks and dynamic discovery mechanisms.
  • The line added to the cover of the directory: the value of a registry depends on the existence of a communication protocol.

In the project

When building an Agent tool system, define the communication protocol first, then fill in the registry. Once the protocol is set (MCP or another standard), adding new tools later is just adding entries to the registry. If you instead accumulate a pile of tools first and patch in a protocol afterward, every tool has a different integration method, and the retrofit cost far exceeds expectations. In review, ask one question: if you swap out a tool implementation, does the Agent need code changes or only registry configuration changes?

京ICP备2026014272号