MCP delivers its greatest architectural value when an AI application must interact with capabilities that exist outside the application's own process , particularly external services, databases, SaaS platforms, APIs, or cloud-hosted tools. Instead of implementing a proprietary integration contract for every agent/tool combination, an MCP server exposes those capabilities using a standardized protocol.

The MCP specification describes the protocol as a standardized mechanism for integrating LLM applications with external data sources and tools . Its tools specification further states that MCP servers can expose capabilities that query databases, call APIs, perform computations, or otherwise interact with external systems.

For trivial local functions such as add() or multiply() , a normal in-process function-tool definition is usually simpler because no separate server protocol is needed. Similarly, an application that has no external dependencies gains relatively little from introducing MCP solely for prompts or local output parsers.

Thus the decisive use case is integration across system or deployment boundaries, especially where capabilities should be reusable by multiple MCP-compatible clients.

Therefore, D is the correct answer and is also explicitly marked correct in the uploaded source.

Study Guide reference/topic: Model Context Protocol (MCP) Fundamentals — external tools, MCP servers, interoperability, reusable integrations, and remote services.

===============