A team needs agents in Microsoft Foundry to call internal inventory and shipping APIs through a standards-based tool interface that can also be reused by other MCP-aware clients. Which implementation best fits?
Select an answer to reveal the explanation.
Short Explanation
You want a standards-based tool interface, so build MCP servers that declare tool schemas, enforce auth, and let Foundry agents call inventory and shipping consistently. Hosting them on Azure Functions, with API Management where appropriate, gives you reusable, governed tools for any MCP-aware client. Free-text URLs in prompts are duct tape, not a tool ecosystem.
Full Explanation
Building tool ecosystems includes MCP servers and clients using Azure Functions, Logic Apps, and API Management. The best fit is building MCP servers, for example on Azure Functions with API Management where appropriate, that declare tool schemas, enforce auth, and let Foundry agents as MCP clients invoke inventory and shipping consistently, making tools reusable and governed. Hard-coding REST URLs in prompts as free text lacks structured tool contracts and secure integration. Emailing CSV exports is manual and non-real-time. Exposing unauthenticated public HTTP endpoints without an MCP contract omits standardization and authentication. Exam tip: MCP + Azure Functions/APIM is a first-class AI-500 development pattern for tool exposure.