Echo Hello MCP Server
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 |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echo_helloC | Echo a hello message |
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 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another. Its purpose (echoing a hello message) is unambiguous.
The single name echo_hello follows a readable verb_noun snake_case pattern. With only one tool there is no cross-tool consistency to evaluate, so it can't earn a full 5.
A single trivial echo tool offers essentially no functional surface. The count is an extreme mismatch for anything resembling a useful server scope.
The tool does exactly what its stated purpose claims, so it isn't a dead end within its own tiny domain. However, there are no adjacent operations (e.g., configurable messages, other greetings) that would make it a real capability surface.