Skip to main content
Glama
Sign In
mcp-registry

mcp-registry

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_mcp_servers

Find MCP servers by name or keywords. Displays matching servers from the registry.

Instructions

Search for MCP servers by name or keywords.

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
queryYesSearch query string.
limitNoMaximum number of results (1-100, default: 50).
registry_urlNoBase URL of the MCP Registry API (default: production).https://registry.modelcontextprotocol.io

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, but the description does not disclose any behavioral traits beyond the basic function. It fails to mention aspects like authentication, rate limits, or side effects. The presence of an output schema mitigates the need for return value details, but the description lacks any additional behavioral context.

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?

The description is a single, clear sentence with no wasted words. However, it could include more context (e.g., mentioning the output type) without becoming verbose. It sacrifices completeness for brevity.

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?

Given the tool has three parameters, an output schema, and no annotations, the description is too minimal. It does not explain search behavior (e.g., fuzzy vs exact), pagination, or result structure. The output schema covers return values, but the description should at least mention that results are returned.

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

Parameters3/5

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

With 100% schema description coverage, the input schema already defines all parameters. The description adds no new semantic value beyond implying the query parameter is used for name/keyword search. The baseline of 3 is appropriate given the schema handles parameter documentation.

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 the action ('Search'), resource ('MCP servers'), and method ('by name or keywords'). It effectively distinguishes from sibling tools like list_mcp_servers, get_mcp_server, and get_server_versions, which serve different purposes.

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 description implies usage for searching, but provides no explicit guidance on when to use this tool versus its siblings. No alternative tools are mentioned, and no conditions (e.g., when list_mcp_servers might be more appropriate) are given.

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

Deploy Server

Other Tools