Lesson 1.1 broke the group-travel team into seven agents, three MCP servers and one flow. Now the question is how they talk to each other. planer calls unterkunft and transport, these call the server lieferanten, kalkulation calls rechner, recht reads travel terms. For each of these connections there is more than one way, and each brings different costs, different errors and a different sign-in. The lesson chooses the ways and records them as a plan that can be checked.

Prior knowledge. "AI track, lesson T8.1" (file 0901, "An MCP server in .NET") explains MCP: host, client and server, tools, resources and prompts, the paths stdio and Streamable HTTP. "T8.2" lets the agent use an MCP server as a client, "T8.3" secures the server with sign-in and permissions. "AI-103, lesson 2.4" introduces the tool types of the Agent Service, "AI-103, lesson 2.5" the approval for MCP tools. What the exam asks beyond that begins here: which protocol where, which components lie in between and how to check the plan.

New in this lesson. The case gets a channel plan with eleven connections: six times intern from planer to the other agents, four times mcp to the three servers from M-04 and once suche from recht to the index reisebedingungen (R-08). A partner agent with A2A does not appear in the case; lesson 2.11 covers integrating existing agents.

The requirement

All numbers are assumptions of the exercise.

No. Requirement Type Measure Weight Source
1.2-01 Every connection of the team has exactly one named protocol. F 0 connections without a protocol Must Exam list
1.2-02 Inside the team, no network call arises that could be a process call. Q 0 A2A connections between agents of the team Should Waiting time, cost
1.2-03 Every access to tools runs through the three servers from M-04, not around them. R 0 tool accesses without a server Must M-04, F-02
1.2-04 The channel plan is checked in the build. R 1 test, red on a forbidden connection Must F-05