When the tool you need is not there

search_tools only returns tools from servers this account has enabled. Omniio's library carries far more than any one account has switched on, and most of them need a credential of their own before they return anything.

So "no results" usually means one of three things, and they need different answers.

1. The server exists but is not enabled

The common case. The library has it; this account has not turned it on.

Tell the user, specifically:

I don't have any Slack tools connected. You can enable Slack at https://omniio.dev/app/library — search for it and switch it on.

Name the product. "You need to connect a server" is not actionable.

2. The server is enabled but not authorized

Some servers are reachable the moment they are switched on because they need no credential. Most need the user to sign in to that product and hand Omniio a token for it. Until they do, the server is enabled but has no tools.

The fix is the same page — https://omniio.dev/app/library — but the action is Connect, not the toggle. Say which one you mean.

Credentials are per person. One member of a team connecting GitHub does not connect it for anyone else.

3. The library does not carry it

The catalogue is curated, not crawled — every entry is a server somebody checked. If a product genuinely is not there, say so rather than guessing at an endpoint, and point them at https://omniio.dev/support to request it.

Do not

• Do not claim a tool exists because the product does. Search first.
• Do not invent a server slug or an endpoint URL.
• Do not tell the user to edit a config file. Connecting a server is done in the Omniio app; their MCP client configuration does not change — the gateway URL stays the same however many servers sit behind it.
• Do not ask them for an API key. Omniio holds credentials; you should never receive one, and a user pasting a token into a chat is a token you have just put somewhere it does not belong.