Skip to main content
Glama

Check an MCP server before connecting

check_server
Read-onlyIdempotent

Read another MCP server's tool list and report what should change how you use it: text aimed at the model, missing safety hints, token cost. Use it before adding a server you don't know. Never calls its tools.

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": {
      "url": "<url>"
    },
    "name": "check_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe server's Streamable HTTP endpoint, e.g. https://mcp.example.com/mcp
budgetNoOptional: flag the list as an error if its definitions cost more tokens than this

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, non-destructive, and openWorld behavior, so the safety bar is pre-lowered. The description still adds real value by promising the remote tools are never invoked and by telling the agent what the report contains, which is important since there is no output schema. It stops short of describing auth requirements or error behavior when the endpoint is unreachable.

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 the action and the payoff, followed by the when-to-use cue and the non-execution guarantee. Nothing is redundant and no sentence could be dropped without losing 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 only two parameters, full schema coverage, and rich annotations, the remaining burden is describing outputs, which the description does at a summary level. It is nearly complete, missing only failure modes for unreachable or non-MCP endpoints.

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 description coverage is 100%, so both url and budget are already documented with format and semantics. The description's mention of 'token cost' loosely ties to the budget parameter but adds no syntax or behavior beyond the schema, so the baseline of 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 uses a specific verb pair ('Read ... tool list and report') on a specific resource ('another MCP server'), and names the three things it reports: model-targeted text, missing safety hints, and token cost. That is far more precise than a sibling like check_stack or get_tool would suggest on name alone, though it never explicitly contrasts itself with those siblings.

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?

'Use it before adding a server you don't know' gives a clear triggering condition, and 'Never calls its tools' sets a boundary on what happens during inspection. There is no explicit when-not or named alternative, but the intended moment of use is unambiguous.

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