Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Echo Tool

echo
Read-onlyIdempotent

Returns the provided message unchanged, enabling you to verify input handling, test client-server communication, or confirm message delivery.

Instructions

Echoes back the input string

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

Input Schema

NameRequiredDescriptionDefault
messageYesMessage to echo

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, covering the safety and side-effect profile completely. The description adds only that the returned value is the input itself, which is the minimum useful behavioral statement and does not mention response shape or any wrapping. A 3 reflects modest added value on top of full annotation coverage.

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?

One short, front-loaded sentence with no filler or repetition. It is arguably too terse rather than too long, but it carries no wasted wording.

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 single-parameter, side-effect-free echo utility with full annotation coverage and no output schema, the description plus the existing hint that the input is returned unchanged is nearly enough to call it correctly. Only minor detail (e.g., whether the response is the raw string or a wrapper) is missing, which is a small gap for a tool of this complexity.

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 (message) with 100% schema description coverage, so the schema already documents it fully. The description's phrase "the input string" loosely corroborates the parameter but adds no format, length, or encoding details beyond the schema; baseline 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?

"Echoes back the input string" states a specific verb (echo) and the resource acted on (the input string), so an agent knows exactly what the tool returns. It stops short of any sibling differentiation, though none of the listed siblings (get-sum, get-env, etc.) appear to overlap, so confusion risk is low.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no mention of the obvious use cases such as connectivity testing or round-trip verification. The agent must infer that this is a diagnostic/utility tool from its name and output behavior alone.

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