Skip to main content
Glama
MCP Echo Service

MCP Echo Service

Echo Message

echo_message

Echoes a supplied message back to the caller, with an optional setting to convert the text to uppercase for testing or display needs.

Instructions

Echo back a message with optional formatting.

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_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe message to echo back
uppercaseNoWhether to convert the message to uppercase

Output Schema

NameRequiredDescriptionDefault
timestampYesISO 8601 timestamp of the echo operation
echoed_messageYesThe echoed message (possibly transformed)
message_lengthYesLength of the original message
original_messageYesThe original message sent
uppercase_appliedYesWhether uppercase transformation was applied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / message / description
      Added value: +"The message to echo back"
    • addedInput schema / properties / uppercase / description
      Added value: +"Whether to convert the message to uppercase"
  2. Addedv0.1.8
  3. Removedv0.1.7
  4. First observedv0.1.5

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 bears the full disclosure burden, and it says nothing about side effects, determinism, or error behavior. For a trivial pure-echo operation the risk is inherently low, and the presence of an output schema covers return values, but "optional formatting" is vague and never explained.

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?

A single front-loaded sentence with no wasted wording. It loses a point only because "optional formatting" is imprecise filler when the schema already names the specific formatting flag.

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?

This is a two-parameter, low-complexity tool with full schema coverage and an output schema, so most of the burden is carried structurally. Still, the description leaves the agent without sibling differentiation or any statement of what "formatting" means, so it is adequate but not complete.

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 description coverage is 100%, so both parameters (message, uppercase) are already fully documented with a default. The description's phrase "optional formatting" gestures at the formatting parameter but adds no syntax or behavior detail beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource ("Echo back a message") plus a scope note ("with optional formatting"), so the agent knows exactly what the tool does. It does not distinguish itself from the siblings echo_json or echo_with_delay, which keeps it from a 5.

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 guidance on when to use this versus echo_json or echo_with_delay, and no stated preconditions. The agent must infer the choice from sibling names alone, which the context notes explicitly say is unreliable.

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