Skip to main content
Glama

mocop

search_capabilities

Read-only

Search everything (APIs, MCP servers, agents, capabilities) for what an agent needs to do.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesNatural language or keyword query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, which cover the safety profile. The description adds only the entity scope of 'everything' and does not explain result behavior, ranking, limits, pagination, or what 'everything' means operationally beyond the parenthetical list.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler. It efficiently states the search scope using a parenthetical enumeration of searchable entity types.

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

Completeness3/5

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

For a simple read-only search tool, the description establishes the broad search domain and annotations cover safety. However, with no output schema and no explanation of result shape or limit behavior, an agent lacks information about what a successful search returns.

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

Parameters2/5

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

Schema description coverage is only 50%: query is documented as natural language or keyword, while limit has only numeric bounds and no description. The tool description does not compensate by explaining what limit controls, how results are capped, or how query text is interpreted.

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

Purpose4/5

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

The description uses a specific verb and resource: search across APIs, MCP servers, agents, and capabilities. It is clear what the tool does, but it does not explicitly distinguish its broad scope from sibling tools such as search_agents, search_apis, or search_mcp_servers.

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

Usage Guidelines3/5

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

The phrase 'for what an agent needs to do' implies the tool is used when looking for capabilities to accomplish a task. However, it gives no explicit when-to-use guidance, exclusions, or comparison with the narrower sibling search tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources