A platform team wants specialist agents in Microsoft Foundry to discover and call a shared set of internal operations (inventory lookup, price quote, order status) through a standardized protocol rather than each agent embedding its own HTTP client and schema. Operations already run as Azure Functions behind Azure API Management. Which design best exposes these operations for multi-agent consumption?
Select an answer to reveal the explanation.
Short Explanation
When every agent rolls its own HTTP client and invents schemas, you get drift, brittle prompts, and security headaches. Model Context Protocol (MCP) is the standard way to publish tools once and let many agents discover and call them with consistent typed contracts. Putting an MCP server in front of your existing Azure Functions (and APIM) keeps the implementation where it belongs while giving agents a clean tool surface. Stuffing raw URLs into prompts is fragile. Dumping source code into memory is unsafe and not how tool ecosystems work. Collapsing everything into one fake chat model throws away real systems of record. Answer B: MCP server + clients over your Functions/APIM stack.
Full Explanation
Correct answer: B. Building and integrating tool ecosystems for multi-agent solutions includes designing MCP servers and clients, including exposures backed by Azure Functions, Azure Logic Apps, and Azure API Management. An MCP server presents stable, typed tools; agents act as MCP clients and call those tools without each reimplementing transport and schema logic.
A is incorrect because hard-coding URLs and informal schemas in prompts produces inconsistent calling conventions, poor validation, and high maintenance cost as APIs evolve.
C is incorrect because long-term memory is not a secure or appropriate vehicle for executable service source code, and agents should call governed tools rather than reimplement backends.
D is incorrect because replacing real operational systems with a single generative model loses transactional correctness, auditability, and integration with inventory and order systems of record.
Exam focus: prefer MCP (or equivalent governed tool surfaces) for shared multi-agent tool access over prompt-embedded HTTP hacks.