mcp-server-template
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Show this server's name, version and data folder, and, for a server that needs programs installed apart, whether they're there. Contains no secrets. |
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
Only one tool exists, so there is no possibility of selecting the wrong tool. The tool's purpose is clear from its name and description.
With a single tool named 'server_info', there is no inconsistency or deviation from a pattern. The snake_case convention is clear and readable.
A single trivial tool ('server_info') is an extreme mismatch for any functional MCP server. The server offers no domain operations, only diagnostic information.
The tool surface is severely incomplete: it only reports server metadata and provides no CRUD or lifecycle operations for any domain. There are no workflows an agent could complete with this server.