Skip to main content
Glama

mocop

search_mcp_servers

Read-only

Search remote MCP servers.

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_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesNatural language or keyword query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured fields. The description contributes only the word "remote", adding nothing about how matching works, whether results are ranked or paginated, or what a returned server entry contains. For a search tool this is thin beyond the annotations.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but its brevity reflects under-specification rather than discipline. There is room for a short clause on result behavior without becoming verbose.

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

Completeness2/5

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

This is a simple two-parameter read tool with annotations covering safety, so it does not need extensive prose, but the description never says what the agent gets back (server entries, endpoints, capabilities) or how the query is interpreted. With no output schema, that return-value context cannot be recovered elsewhere.

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 in the schema while limit is not, and the description says nothing about either. It does not clarify that limit caps result count, nor what natural-language vs keyword matching means in practice, so it fails to compensate for the coverage gap.

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?

"Search remote MCP servers" gives a specific verb (search) and a specific resource (remote MCP servers), which is enough for an agent to grasp the tool's function. It does not distinguish itself from lookalike siblings such as search_agents or search_apis, so the agent must infer the boundary from the resource noun alone.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no exclusions, and no mention of when a sibling search tool would be the better choice. An agent facing several search_* tools receives no routing signal whatsoever.

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