example-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXAMPLE_LOG_LEVEL | No | The log level for the server. Can be 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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| example_echoC | 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
With only a single tool, there is no possibility of confusion or overlap with other tools. The purpose of example_echo is clear and distinct.
The single tool name follows a verb_noun pattern (example_echo), which is consistent and readable. However, with only one tool, consistency across a set cannot be fully established.
At one tool, this server is at the borderline of being too thin. While a minimal example server might justify a single tool, it feels sparse compared to typical well-scoped servers.
The server is explicitly a placeholder with a single echo tool and no clear domain coverage. It has no CRUD operations, no real workflow support, and would fail any practical task beyond echoing text.