AgentforceAdvancedmcpheadlessintegration
Troubleshoot MCP tool invocation failures in headless agent integration
Real World Scenario
External mobile app uses Agentforce via MCP; intermittent "tool not found" errors when custom action renamed in Salesforce org.
Expected Answer
• Version MCP tool schema with breaking change detection in CI
• Client pin compatible agent API version
• Health check endpoint listing available tools before session start
• Graceful client fallback when tool missing
• Rename actions with deprecation period dual-register old name
• Monitor MCP error rates by tool name in observability stack
• Document external integration contract like public API
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Version MCP tool schema with breaking change detection in CI Also consider: Client pin compatible agent API version In practice: Health check endpoint listing available tools before session start Optimize for scale and operational observability.
Architect Perspective
Headless agents are API products — tool renames are breaking changes requiring client coordination.