A team needs agents in Microsoft Foundry to call internal inventory…

Question

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?

Accepted Answer

Build MCP servers (for example hosted on Azure Functions, with API Management where appropriate) that declare tool schemas, enforce auth, and let Foundry agents (MCP clients) invoke inventory and shipping operations consistently. — Correct answer: D. MCP is the USB-C of tools: one schema’d, authenticated server (often on Azure Functions + APIM) and any compliant agent client can plug in. Free-text URLs in prompts are duct tape, not a tool ecosystem.

Answer

Hard-code REST URLs only inside each agent prompt as free text with no schema or auth.

Answer

Email CSV exports to the agent authors whenever inventory changes so they can paste numbers into prompts.

Answer

Expose tools only as unauthenticated public HTTP endpoints without an MCP contract.

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?

Short Explanation

Full Explanation