mcp-server-template
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Log level for the server: debug, info, warn, or error. Logs go to stderr at every level. | 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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Return the input text unchanged. Use this to confirm the server is connected. |
| nowA | Current date and time in an IANA time zone, such as Asia/Kolkata or UTC. |
| uuidA | Generate a random UUID v4. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-diff | Ask for a review focused on correctness, not style. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| manifest | Name, version, license, and runtime of this server. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: connectivity check, current time retrieval, and UUID generation. There is no plausible scenario where an agent would confuse one for another.
All three names are single lowercase words following the same terse style, so the set is internally predictable. It deviates from a verb_noun convention, but consistency is high with no mixed casing or styles.
Three tools is thin for a functional server, though defensible for a template/starter server whose purpose is minimal demonstration. It borders on under-scoped relative to a general utility server.
Each tool is self-contained with no lifecycle gaps (nothing to create/update/delete), but the surface is notably minimal—no timezone conversion, formatting, or typical utility operations beyond these three primitives.