Skip to main content
Glama

Agent Web Census

find_mcp_servers

Read-only

Search the official MCP Registry (~65,000 servers) by keyword. Matches name, title and description; ranks servers whose remote endpoint passed a live initialize check first, then by number of tools. Returns name, title, description, remote/package types, health (ok = works without auth, auth = alive but needs auth, fail = unreachable), tool count and a registry link.

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": "find_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-25).
queryYesKeywords, e.g. 'postgres database' or 'github issues'.
categoryNoOptional category filter, e.g. 'finance & crypto', 'databases' (substring match).
transportNoremote = hosted endpoint, package = installable (npm/pypi/...), any (default).
working_onlyNoOnly servers whose remote endpoint responded OK or requires auth (default true). Package-only servers are kept unless transport is 'remote'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing ranking rules (remote endpoints that passed a live initialize check first, then tool count) and defining the health field semantics (ok = works without auth, auth = alive but needs auth, fail = unreachable). That is exactly the kind of operational detail an agent needs to interpret results.

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 dense sentences, front-loaded with purpose, then matching/ranking, then return shape. No filler; the length is justified because there is no output schema to carry the return-value explanation.

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?

With five parameters, no output schema, and a read-only annotation profile, the description covers purpose, ranking, return fields, and health-code meaning. Nothing an agent needs to call or interpret the tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by tying 'query' to the fields actually matched and explaining how results are ordered. It does not restate the limit/transport/category constraints, but the schema already handles those.

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?

States a specific verb and resource ('Search the official MCP Registry') plus scale (~65,000 servers) and match scope (name, title, description). This is clearly distinguishable from sibling stats/policy tools.

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?

Provides clear context for when to reach for this tool: keyword discovery of MCP servers, with matching and ranking behavior spelled out. It does not name exclusions or alternatives, but the sibling tools are stats/policy oriented, so the gap is minor.

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.