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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dataB | Retrieve data from your custom data source with optional filtering and pagination. |
| get_system_infoA | Get system information and utilities. Provides current date, timezone, and other helpful context. |
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 2 tools
The two tools serve entirely different purposes: one retrieves data, the other provides system information. There is no overlap or ambiguity, so an agent can easily distinguish them.
Both tool names follow the same 'get_' prefix followed by a noun, resulting in a consistent naming convention.
With only two tools, the set feels minimal and thin. While it is a boilerplate, the number is at the lower edge of the typical range, making it borderline.
The tool surface is very limited: it offers only retrieval operations for data and a single system info utility. There are no create/update/delete operations for data, and the tools do not form a coherent workflow, leaving significant gaps for real use.