Skip to main content
Glama

InterfaceDelta canary (test server)

Echo text

echo_text
Read-onlyIdempotent

Returns the text it is given. Test tool from InterfaceDelta.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the framing that this is a test tool, and says nothing about the 500-character limit behavior (e.g. whether input is rejected or truncated) or the exact response shape. With annotations carrying the load, this is adequate but adds minimal context.

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?

Two short sentences, front-loaded with the core behavior and followed by the one piece of context that matters. No filler or redundancy.

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?

For a trivial one-parameter passthrough with a complete annotation set and no output schema, the description covers the essential contract: input text in, same text out. The only omission is boundary behavior at maxLength 500, which is minor for this complexity level.

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 one parameter with 0% schema description coverage, so the schema only supplies a name and a maxLength of 500. The description clarifies that the text is echoed back verbatim, which explains the parameter's role, but it says nothing about what happens at the length boundary or whether the value is validated. That is a partial compensation for the coverage gap.

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 behavior — it returns the input text unchanged — which confirms this is a pure passthrough with no transformation. It is close to restating the name 'Echo text', but it also rules out any hidden formatting or processing, which is meaningful for a tool whose whole contract is identity. It is distinguishable from siblings like add_numbers and get_time by implication.

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?

The phrase 'Test tool from InterfaceDelta' signals the intended context (testing/verification rather than production use), which is real usage guidance. However, it never states when to prefer this tool over the siblings or any preconditions for calling it. Guidance is implied rather than explicit.

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