MCP Server Boilerplate
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| echo |
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, as there are no other tools to compare it against. The tool 'echo' stands alone with no ambiguity in its purpose relative to other tools in the set.
Since there is only one tool named 'echo', there is no inconsistency in naming patterns to evaluate. The tool name follows a simple, single-word convention, and with no other tools, it cannot be inconsistent.
A single tool named 'echo' with no description suggests a minimal or trivial server, which may be insufficient for most practical purposes. While it could be appropriate for a very narrow scope, it likely feels thin and underdeveloped for typical MCP server use cases.
With only one tool and no description provided, it is impossible to assess coverage of any domain. The tool set is severely incomplete, as there are no other tools to form a coherent surface, and the lack of description makes it unclear what functionality is even intended.