Skip to main content
Glama
MCP Echo Service

MCP Echo Service

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
echo_messageB

Echo back a message with optional formatting.

echo_with_delayB

Echo back a message after a simulated delay.

echo_jsonC

Echo back structured JSON data with validation and analysis.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation4/5

Each tool targets a distinct echo behavior: plain message echo, delayed echo, and structured JSON echo with validation. The only soft overlap is that echo_with_delay is essentially echo_message plus a timing parameter, which could lead an agent to pick either for a simple delayed echo.

Naming Consistency4/5

All three tools share a clear 'echo_' prefix with a predictable suffix, giving a coherent family (echo_message, echo_with_delay, echo_json). The 'with_' connector in echo_with_delay is a minor stylistic deviation from the noun-suffix pattern but remains readable.

Tool Count4/5

Three tools is well within a sensible range for a small echo/diagnostic service and each covers a genuinely different output mode. The set is slightly thin, and the delay variant arguably could be a parameter rather than its own tool.

Completeness4/5

The domain is echoing, and the surface covers plain text, delayed responses, and validated/analyzed JSON, which handles the obvious use cases without dead ends. Minor gaps (e.g., no explicit bulk or formatting-only operation) are workable through the optional formatting on echo_message.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues