Skip to main content
Glama

allMCPservers directory

Search MCP servers

search_mcp_servers
Read-onlyIdempotent

Search the allMCPservers directory of MCP servers from the Official MCP Registry and Claude's Connectors Directory. Returns matching servers with their slug, publisher, category, transport and profile link. Leave out query to browse, editor's picks first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNoResults per page.
queryNoWords to look for in names and descriptions, such as "postgres" or "browser automation".
sourceNoOnly servers listed in the Official MCP Registry (registry) or Claude's Connectors Directory (claude).
categoryNoOnly servers in this category. list_categories describes each one.
transportNoremote: a hosted endpoint you connect to by URL. local: a package you run on your machine. Servers offering both match either.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered elsewhere. The description adds value beyond them by disclosing the result shape and the ordering behavior when browsing (editor's picks first), which an agent cannot infer from the schema. It doesn't discuss pagination totals or result caps, a minor omission.

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?

Three short sentences, front-loaded with what is searched and where the data comes from, then return fields, then the browsing hint. No filler or redundancy; each sentence carries distinct information.

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

Completeness4/5

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

With no output schema, the description correctly takes on the burden of describing return fields and default ordering, which it does. Combined with a well-described six-parameter schema and read-only annotations, an agent has what it needs; only pagination/cap behavior is left implicit.

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?

Schema coverage is 83%, with descriptions on limit, query, source, category and transport, so the schema already carries most parameter meaning. The description contributes only the semantics of omitting query (browse mode). It adds nothing about how source or transport filters interact with query, so the baseline 3 applies.

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 names a specific verb and resource — searching the allMCPservers directory — and scopes it to two named upstream sources (Official MCP Registry, Claude's Connectors Directory). It also enumerates the returned fields (slug, publisher, category, transport, profile link), so the agent knows what it gets back. It does not explicitly distinguish itself from siblings like get_mcp_server or compare_mcp_servers, which keeps it below a 5.

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

Usage Guidelines4/5

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

It gives one concrete conditional: omit the query to browse, in which case editor's picks come first. That is actionable context for a common invocation pattern. It stops short of naming alternatives (e.g., list_categories for category discovery, which is only referenced inside the schema) or stating when not to use it.

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