Plugging in the world: AI Engineering, story 10
One question needs the orders system, the store calendar and the courier. See how the assistant reaches all three without custom wiring for each.
One standard plug (MCP) lets any assistant use any tool.
The story, step by step
One question, three systems
HM Nayem wants to collect an order in store on Saturday. Answering needs the order system, the store's booking calendar, and maybe the courier. Three systems, built by three different teams.
The hand-wired way
In the last story the shop wired up one tool by hand. That means describing it for the model, translating each request, and handling errors. Now multiply: every system, for every assistant the shop runs.
A standard plug
The Model Context Protocol, MCP, is a standard plug. Each system gets one small connector, called an MCP server, that speaks a common language. Any assistant that speaks it can plug in.
First, ask what is on offer
On connecting, the assistant asks each one the same standard question: what tools do you have? Each replies with names, descriptions and inputs. Nobody at the shop wrote this menu by hand.
What a connector says about a tool
Here is what one connector sent back. A name, a plain description, and the inputs it needs. It is exactly the kind of menu entry the shop wrote by hand in the last story. Now it arrives ready-made.
The model orders from the menu
The whole menu goes to the model with the question. It asks for two tools at once: one from the order system, one from the calendar. To the model they look exactly alike.
One way to call them all
The assistant passes each request through the same standard call. It does not need to know how the calendar stores bookings or how the order system is built. The connectors handle that.
The answer
Both results go back to the model, and it writes one clear reply from the two of them. HM Nayem asked one question and never saw that three systems stood behind it.
Why the plug matters
Each system is connected once and works with every assistant. And the courier's connector was written by the courier. A tool someone else built plugs into the shop's assistant unchanged.
Now at real speed
One question, one menu, two tools called side by side, one answer. The plug is invisible when it works, which is the whole point of a standard.
One plug, and any tool fits.
- Hand-wiring every tool to every assistant does not scale.
- MCP gives each system one connector that speaks a common language.
- The assistant asks each connector what tools it has, then offers them all to the model.
- Independent requests can be run side by side, so the answer comes sooner.
Ideas in this story
- Model Context Protocol: A standard plug between assistants and tools, so each tool is connected once and works everywhere.
- Tool calling: The model cannot do anything itself. It asks your code to, and your code answers.