example-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXAMPLE_LOG_LEVEL | No | Log level: INFO (default) or DEBUG. | INFO |
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 |
|---|---|
| example_echoB | Return the text you pass in. Replace with real tools. |
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
Only one tool exists, so there is no possibility of confusion between tools. The single tool clearly performs an echo operation with no overlapping purposes.
The sole tool name 'example_echo' does not follow a clear verb_noun pattern ('example' is not a verb), but there is no inconsistency to compare against. The name is readable but not representative of a standard naming convention.
With only one tool, the server is far below the typical scope of 3-15 tools. The tool appears to be a placeholder, and the count feels excessively thin for a functional MCP server.
The description explicitly states 'Replace with real tools,' indicating this is a stub rather than a complete domain surface. There is no coherent set of operations to cover a real workflow, leaving significant gaps for any practical use.