Skip to main content
Glama

MCP server reliability and identity

mcp_servers
Read-onlyIdempotent

Which remote MCP servers the official MCP Registry lists on a domain, and what each endpoint actually answered when CrawlCheck sent the MCP handshake (initialized, auth_required, unreachable, tool count, tool-list drift). Use before selecting an MCP tool from that domain.

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": {
      "domain": "<domain>"
    },
    "name": "mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain or host, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the description earns credit for adding what those flags cannot: the tool actively performs a live MCP handshake against remote endpoints and reports discrete outcome states, and it detects tool-list drift, implying comparison over time. It does not disclose latency, cost, or whether the probe is rate-limited, and there is mild tension with openWorldHint=false given that remote endpoints are contacted.

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?

Two clauses, front-loaded with what is returned, followed by the usage trigger; there is no filler. The long parenthetical enumerating outcome states is information-dense but slightly hurts scannability compared with a short lead sentence plus a bulleted set of states.

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 must carry return values, and it does list the expected states and signals an agent would consume. It leaves the response shape and per-field meaning implicit, but for a single-parameter read-only probe this is close to complete.

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?

Only one parameter (domain) exists and schema description coverage is 100%, with the schema already giving format guidance ("Bare domain or host, e.g. example.com"). The description adds no further meaning about normalization, subdomains, or what happens on an unregistered domain. Baseline 3 is appropriate when the schema already carries the load.

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 resource (remote MCP servers listed by the official MCP Registry for a domain) plus the concrete artifact returned (per-endpoint handshake results: initialized, auth_required, unreachable, tool count, tool-list drift). That is far more specific than a restated title. It does not name or contrast against likely-adjacent siblings such as registry_lookup, list_verified_capabilities, or preflight, so it stops short of 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 Guidelines3/5

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

"Use before selecting an MCP tool from that domain" gives one explicit trigger, which is genuinely useful sequencing guidance. There is no when-not guidance, no mention of what to do if the domain has no listed servers, and no routing to alternatives like preflight or registry_lookup, so usage is implied rather than fully specified.

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.