Skip to main content
Glama

toolport_search_tools

Search across MCP servers by capability keywords to find and call the right tool. Returns matching tool names, descriptions, and input schemas.

Instructions

Your single gateway to every connected MCP server and ALL their tools. Try this FIRST for ANY external action or data the user asks for - sending or listing email, deployments, payments, databases, repos, issues, files, web search, etc. Do NOT reach for an unrelated tool or tell the user a capability is unavailable until you have searched here; if the service is connected, its tool is here. Returns matching tools with their exact name, description, and input schema; call one with toolport_call_tool. Once a result matches what you need, call it - do NOT keep searching for a better one (the first result includes its full schema and is ready to call). Pass server (a name/prefix like "resend") to scope to one server, and pass an EMPTY query with server to list ALL of that server's tools. If the result says more tools matched than were shown, narrow with server or raise limit before concluding a capability is missing - many servers expose a generic API bridge (a single write/create tool), so search by capability, not just an exact operation name. toolport_status lists every server prefix and its tool count. Large input schemas may be omitted from broad results (flagged schemaOmitted) to keep responses small - search a tool's exact name to get its full schema.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 25, up to 200).
queryYesKeywords describing the capability you need (e.g. "list emails", "create payment", "recent deployments"). Empty lists tools (use with `server`).
serverNoOptional: limit to this server, by name/prefix (e.g. "resend").
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses that large input schemas may be omitted (schemaOmitted) and suggests searching exact name for full schema. Also notes that many servers expose generic API bridges. Does not mention any side effects or auth needs, which is acceptable for a read-only search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is lengthy but every sentence provides valuable guidance. It front-loads the main purpose and then offers detailed strategies. Could be slightly more concise, but efficient given the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's role (search across multiple servers) and lack of output schema, the description is remarkably complete. Covers scoping, handling incomplete results, schema omission, and integration with sibling tools. Leaves no major gaps for an AI agent to misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds extra: explains empty query with server to list all tools, gives usage examples ('list emails'), and clarifies limit range (default 25, up to 200). Adds value beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is the gateway to all MCP servers' tools, using verbs like 'search' and 'list'. It distinguishes itself from siblings (toolport_call_tool, toolport_status) by specifying its role as the discovery entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit directives: use this FIRST for any external action, do not assume capability missing until searched, once matched call it without further searching. Gives strategies like using server scope, empty query, or raising limit. Mentions sibling toolport_status for listing servers.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tsouth89/toolport'

If you have feedback or need assistance with the MCP directory API, please join our Discord server