Skip to main content
Glama

Echo

echo

Return any message unchanged to verify agent connectivity and message routing across shared MCP sessions. Confirms the daemon is reachable and echoes your input verbatim.

Instructions

Return the input

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

Input Schema

NameRequiredDescriptionDefault
msgYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no indication of whether the call is side-effect free, whether output is synchronous, or whether anything is persisted. The single clause does at least imply the return value mirrors the input, which is the only behavioral signal present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two words are technically waste-free, but this is under-specification rather than conciseness. Nothing is front-loaded because there is essentially no content to structure.

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

Completeness2/5

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

The tool is simple (one required string, no output schema), so the bar is low, yet the definition still omits what is actually returned and what the tool is for. A single clarifying sentence about the echo semantics would have made it complete.

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?

Schema description coverage is 0%, so the description must compensate, and it does not. It never names the required 'msg' parameter, its type, or any constraint such as size or encoding, leaving the schema as the only source of truth.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Return the input" restates the tool name 'echo' rather than defining a distinct verb and resource. It does not clarify whether the input is returned to the caller, logged, or echoed into the surrounding channel/messaging ecosystem implied by siblings such as broadcast and send_message.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no exclusion, and no named alternative. An agent cannot tell whether this is a connectivity check, a logging utility, or a messaging primitive.

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