Skip to main content
Glama

hello

Verifies that the MCP server is running correctly by accepting a name value and returning a test response.

Instructions

测试工具 - 验证 MCP 服务器是否正常运行

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full burden of behavioral disclosure. It conveys that the call is a non-destructive health check, which is useful, but it says nothing about side effects, whether a failed verification signals that the server is unavailable, or what the response indicates; the output schema covers return values, which limits the severity of the last gap.

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?

The description is one short sentence, front-loading the tool category before the purpose, with no filler. The extreme brevity is a deficiency of substance rather than of structure, and that deficiency is assessed elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple: it has one parameter and an output schema, so return values need no explanation. Even so, the description leaves the required 'name' argument and the relationship to the existing server-status sibling unexplained, which leaves it only borderline adequate.

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

Parameters2/5

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

The schema has one required parameter, 'name', and no per-field description in the schema; the description adds no information about it. The agent cannot tell whether 'name' is a client name, a username, or a server identifier, so it must guess; the description does not compensate for the 0% schema coverage.

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 states a specific action and purpose: a test tool that verifies whether the MCP server is running normally. That action is recognizable and specific, but it does not distinguish this tool from the sibling check_server_status, which appears to perform a similar health-check function.

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?

Saying the tool is a 'test tool' for verifying server operation only implies when to use it; the definition gives no explicit trigger or exclusion, and it never mentions how this differs from check_server_status or when an agent should prefer one over the other.

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