Skip to main content
Glama
MCP Echo Service

MCP Echo Service

Echo With Delay

echo_with_delay

Echoes a provided message after a configurable delay of up to 5 seconds, useful for testing delayed responses and MCP protocol timing behavior.

Instructions

Echo back a message after a simulated delay.

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

Input Schema

NameRequiredDescriptionDefault
messageYesThe message to echo back
delay_secondsNoDelay duration in seconds (max 5.0 seconds)

Output Schema

NameRequiredDescriptionDefault
end_timeYesISO 8601 timestamp when delay ended
timestampYesISO 8601 timestamp of the operation
start_timeYesISO 8601 timestamp when delay started
actual_delayYesActual delay experienced in seconds
echoed_messageYesThe echoed message
requested_delayYesRequested delay in seconds
original_messageYesThe original message sent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / delay_seconds / description
      Added value: +"Delay duration in seconds (max 5.0 seconds)"
    • addedInput schema / properties / message / description
      Added value: +"The message to echo back"
  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 carries the burden. It discloses that the delay is simulated, which is useful, but says nothing about whether the call blocks the caller, that the delay is capped at 5 seconds (only in the schema), or what the response contains beyond the echoed message.

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 well-formed sentence with no filler, front-loading the action and the key behavioral trait. It is efficient, though extremely terse for a tool with a configurable delay.

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 simple two-parameter tool with full schema documentation and an output schema, the description covers the essentials. The only meaningful omissions, blocking behavior and sibling selection, are minor given the tool's triviality.

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%, with both 'message' and 'delay_seconds' (including the 5.0 second cap and default of 1) documented in the schema itself. The description adds no meaning beyond that, 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 the distinguishing trait of a 'simulated delay' that differentiates it from echo_message/echo_json. It is clear but never explicitly contrasts itself with those siblings.

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 guidance, no mention of when to prefer echo_message or echo_json, and no note that this is for testing latency or timing behavior. The usage is only implied by the tool name and the delay parameter.

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