Unit 01 of 02
Protocol Structure
Counting the standardization of tool connections by splitting it into roles and layers: the requests, responses, envelope tokens and round trips the same three-tool chain pays against the baseline without the protocol, and how many clients it takes to measure the portability gained in return; which item sits in which role among the host application, client and server, and the messages each item crossing a role boundary adds; the request count staying fixed between local and remote transport while the round trips double; the per-message cost of the request, response and notification types, and what the notification's lack of a response saves and makes invisible; three of five declared tools being understood, version skew dropping an entire server without producing any error, and the tool the allowlist drops in addition.
Published Updated
Lessons
- 01 What Is the Model Context Protocol Counting what happens when the tool definition leaves the calling side for a server: three servers declare five tools, the allowlist carries four, negotiation leaves three. The same chain gives 844 with zero messages at the baseline; with the protocol it costs 6 requests, 6 responses, 179 envelope tokens and 9 round trips. Across four clients the setup without the protocol breaks four places, the setup with it one. 4 min read
- 02 Host, Client and Server Counting the division of responsibility among the three roles by messages: ten items are distributed, the correct distribution needs no negotiation message, and every item that crosses a role boundary adds messages equal to its scope times its distance. Gathering all ten items in one role piles up 51 messages in the host, 45 in the server, 33 in the client, and zero in the correct distribution. The same three-tool chain costs 6 requests, 6 responses, 179 envelope tokens and 9 round trips in the correct distribution, and 12, 12, 341 and 15 with the allowlist on the server. 9 min read
- 03 Transport Layer Comparing local and remote transport in round trips on the same workload: the same three-tool chain gives 844 with 6 requests, 6 responses and 179 envelope tokens in all three transport setups, but round trips are 6 all local, 9 mixed and 12 all remote. Requests stay fixed while round trips exactly double. In a twelve-subscriber batch requests hold at 39 while round trips go from 39 to 78. The dropped kayit server still costs 1 round trip local and 2 remote. This lesson is the first example of the course's second claim: standardizing also breaks. 4 min read
- 04 Data Layer Counting the cost of request, response and notification messages: an eight-subscriber batch is 24 function calls and zero messages without the protocol, and 48 messages, 640 tokens and 32 round trips with it, 384 of the 640 tokens being envelope alone. The same progress information costs 1147 tokens and 80 round trips as request-response pairs and 976 tokens and 32 round trips as notifications. Its price is that five notifications dropped on the line leave no trace on the sender. 4 min read
- 05 Server Capabilities Counting the difference between declared and agreed capabilities: three fictional servers declare 5 tools, 2 resources and 1 prompt, the allowlist holds 4 tools, and the handshake yields 3. Both runs pay the same cost — 3 requests, 3 responses, 99 tokens, 5 round trips, 0 errors — but their results diverge: with aligned versions 4 tools are agreed and the allowlist drops kayit_yaz on purpose; with version skew the whole kayit server drops and bolge_ozet, which is on the allowlist, vanishes without any error. If olcum drops, the agreed tools fall to 2. Both losses give the same error text, one deliberate and one an accident. 8 min read