MCP Echo Service
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echo_messageA | Echo back a message with optional formatting. Args: message: The message to echo back uppercase: Whether to convert the message to uppercase ctx: MCP context Returns: Complete echo response with metadata |
| echo_with_delayA | Echo back a message after a simulated delay. Args: message: The message to echo back delay_seconds: Delay duration in seconds (max 5.0 seconds) ctx: MCP context Returns: Echo response with timing information |
| echo_jsonB | Echo back structured JSON data with validation and analysis. Args: data: The JSON data to echo back ctx: MCP context Returns: Echo response with data analysis |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: echo_json handles structured JSON with analysis, echo_message handles plain text with optional formatting, and echo_with_delay adds a timing component. There is no ambiguity or overlap between the tools.
All tool names follow a consistent 'echo_' prefix with snake_case, and each name clearly indicates its function (json, message, with_delay). The pattern is predictable and uniform.
With 3 tools, the server is well-scoped for an echo service. Each tool provides a distinct mode of echoing, covering the basic needs without being overly numerous or sparse.
The tool surface covers the core use cases for an echo service: plain text, JSON, and delayed echoing. There are no obvious missing operations given the server's simple purpose.