2761 - MCP 和工具调用的有效 API 策略.pdf

《2761 - MCP 和工具调用的有效 API 策略.pdf》由会员分享，可在线阅读，更多相关《2761 - MCP 和工具调用的有效 API 策略.pdf（17页珍藏版）》请在三个皮匠报告上搜索。

1、IBM Data&AI|2025 IBM CorporationEffective API Strategies for MCP and Tool Calling 2761Mansura Habiba,IBMhttps:/ Context ProtocolMCP=Model Context ProtocolMCP servers give access to data,often by wrapping existing programming interfaces such as APIs or SDKsMCP=Model Context ProtocolMCP servers can be

2、 run local or remote,with different transport layers(SSE will be deprecated)MCP=Model Context ProtocolMCP Clients can connect to MCP servers using one of the transport layers from a host application(chat app,IDE,agent,etc)MCP is one of the most viral technologiesMCP was announced in November 2024.Mi

3、crosoft,GitHub,AWS merged PRs since February 2025.Many teams at IBM are building with MCPhttps:/ building MCP servers has its challenges.Local vs.Remote MCP servers Security:central policy engine,secret management,signed/audited traces,authentication,authorization Spec drift and compatibility:MCP ev

4、olves;clients and servers may implement different subsets.Contracts:schema validation,golden examples,dry-run simulator Reliability:async+parallelism,circuit breakers,idempotency keys Observability:E2E trace IDs,prompt/tool I/O logs with PII controls Governance:versioned prompts/tools/policies,stage

5、d rollout&rollback Tool Orchestration:planning,sequential thinking,workflow,tool call optimization Compliance:data residency routing,source tagging,retention policiesAlso APIs are different from MCP tools Agents plan and chain tools autonomously across products and tenants Latency and error surfaces

6、 compound across hops Inputs and outputs must be machine-steerable not just human-readable Policies and audit must travel with the call context Contracts need to be small,strict and composable No longer driven by fixed button or instruction a prompt can be anythingIf a planner cannot infer inputs,pr