Skip to main content
Glama

Check MCP server

check_mcp_server

Connect to a remote streamable-HTTP MCP server: initialize, notifications/initialized, and tools/list. Also lists prompts or resources when advertised. Never calls the remote server's 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_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRemote MCP endpoint, for example https://example.com/mcp.

Output Schema

NameRequiredDescriptionDefault
okNo
toolsNo
errorsNo
latency_msNo
server_infoNo
capabilitiesNo
auth_requiredNo
protocol_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the exact handshake sequence, that prompts/resources are listed only 'when advertised', and that remote tools are never invoked, so the agent knows there is no side effect on the remote server. It omits auth requirements and failure behavior for an HTTP connection, which is a real but modest gap.

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 with the core action front-loaded and the scoping caveat placed last. No filler or restatement of the title.

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?

An output schema exists, so return values need no explanation, and the description covers the operation and its boundary clearly. The only missing piece an agent might want is whether the endpoint requires authentication or what happens on connection failure.

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?

There is a single parameter at 100% schema coverage, and the schema already describes it as a 'Remote MCP endpoint' with an example. The description adds only the 'streamable-HTTP' qualifier, so it does not meaningfully extend the schema's meaning.

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 names a specific verb and resource ('Connect to a remote streamable-HTTP MCP server') and enumerates the exact protocol steps performed (initialize, notifications/initialized, tools/list). The resource is unambiguous enough to distinguish it from generic siblings like check_url or fetch_page without naming them.

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?

It states a clear scope boundary ('Never calls the remote server's tools'), which implicitly tells the agent this is a discovery/inspection tool rather than an execution tool. However, it never says when to prefer this over check_url or site_discovery, nor does it name any alternative, so the routing guidance is only implied.

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