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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo a message back to the caller |
| timestampA | Get the current UTC timestamp |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| info |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one echoes messages, the other returns timestamps. There is no overlap or ambiguity.
Both tool names are single-word lowercase verbs ('echo', 'timestamp'), following a consistent and predictable pattern.
With only 2 tools, the set is minimal, but as a boilerplate or template, each tool serves a clear and essential purpose. It is slightly under the typical range but reasonable for its intended use.
For a boilerplate server, the tool surface is complete: it provides basic demonstration functions (echo and timestamp) with no missing operations.