my-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | The connection string for the database tool example. | |
| WEATHER_API_KEY | No | The API key for the weather tool (used by the OpenWeatherMap API example). | |
| MCP_TRANSPORT_MODE | No | The transport mode for the server. Set to 'http' to use HTTP mode with WebSocket MCP endpoint; otherwise defaults to stdio. |
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 |
|---|---|
| echoB | Echo a message back to the client. Args: message: The message to echo Returns: The echoed message with any configured prefix |
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 one tool, there is no possibility of confusion or overlap between tools. The 'echo' tool has a clear, singular purpose that is distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'echo' is straightforward and follows a simple verb pattern.
One tool is generally too few for a meaningful MCP server, as it offers minimal functionality and likely does not cover a useful domain comprehensively. This feels thin and under-scoped for most practical purposes.
The server is severely incomplete, as a single 'echo' tool does not define a clear domain or provide any meaningful coverage. There are obvious gaps, as no operations beyond echoing a message are available, making it trivial and non-functional for agents.