A real feature usually needs more than one API. Rather than search for everything at once, a good agent breaks the request into one focused query per capability.

1. Ask your agent:

   Copy prompt

   I'm building a booking confirmation flow: when a desk is booked, create a calendar event for that time slot, and post a message to a Slack channel announcing the booking. Use the Orbit MCP tools to find endpoints for this: search for each capability separately, don't cram them into one query.

2. Confirm your agent makes two separate search calls (one for the calendar capability, one for the Slack capability) rather than one combined or OR-joined query.

Troubleshooting: If your agent sends one jumbled query for both capabilities, tell it to split the request and re-run.

The Not supported: line is what prevents a wasted integration, so make your agent surface it before it commits to an endpoint.

1. Ask your agent:

   Copy prompt

   For each capability, list the top 2-3 candidates with their evaluateGuide, leading with what each one does NOT support.

2. Confirm the agent's summary leads with limitations, not just the happy path, and that it picks one endpoint per capability that has no disqualifying gap for this task.