Skip to main content
Glama

test_mcp_server

Performs a real MCP handshake and lists external tools to verify connectivity, authentication, and protocol compatibility. Updates server status and error details for troubleshooting.

Instructions

Perform a real MCP handshake and list external tools to check connectivity, authentication and protocol compatibility. Updates the stored server status, last error and protocol version. success=true means the test ran; reachable is its result. Inspect error_class and error_message when unreachable.

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": {
      "mcp_server_id": "<mcp_server_id>"
    },
    "name": "test_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
mcp_server_idYesUUID of the MCP server to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / mcp_server_id / description
      Previous value: -"UUID do MCP server a testar"New value: +"UUID of the MCP server to test"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a mutating, non-idempotent, open-world call, and the description usefully adds that it writes server status, last error and protocol version as a side effect. It also clarifies the easily-confused success vs. reachable semantics, which annotations cannot convey. Not stated: whether testing has auth/prerequisite requirements or cost on the target server.

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?

Four short sentences, front-loaded with what the tool does, then side effects, then result interpretation. Every sentence carries information; minor terseness in the 'success=true means the test ran' phrasing is the only friction.

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 supplies the return-value interpretation (success vs. reachable, error_class, error_message) that an agent needs to act on results. It is nearly complete, though it omits any indication of error_class values or how long the test takes.

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 100% for the single mcp_server_id parameter, so the schema already carries the semantics. The description adds no further detail about the identifier, so the baseline 3 applies.

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 concrete action chain ('perform a real MCP handshake and list external tools') plus the goal ('check connectivity, authentication and protocol compatibility'). This clearly distinguishes it from CRUD siblings like get_mcp_server or create_mcp_server, which only manage records.

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?

Usage context is clear: run it to verify a server is reachable and protocol-compatible, and inspect error_class/error_message when the result is unreachable. It does not name alternatives (e.g., test_trigger) or state when not to run it, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools