MCP Boilerplate Server
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 |
|---|---|
| greetB | Greet a person by name |
| addB | Add two numbers together |
| multiplyB | Multiply two numbers together |
| get_user_infoB | Get user information by ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_user_data | Generate a prompt to analyze user data with specified analysis type |
| generate_user_report | Generate a prompt to create a user report for multiple users |
| system_health_check | Generate a prompt to check system health for specified components |
| troubleshoot_issue | Generate a troubleshooting prompt for server issues |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_server_info | Provides information about this MCP server |
| get_all_users | Provides a list of all available users |
| get_server_settings | Provides server configuration settings |
TDQS
Scored across 4 tools
The tools have unclear boundaries and overlapping purposes. 'add' and 'multiply' are distinct mathematical operations, but 'get_user_info' and 'greet' are unrelated to them and to each other, creating a confusing mix of domains. An agent might struggle to choose between tools for different tasks due to the lack of a cohesive theme.
The naming is inconsistent with mixed conventions. 'add' and 'multiply' use simple verb forms, while 'get_user_info' follows a verb_noun pattern and 'greet' is a standalone verb. This lack of a predictable pattern makes the tool set harder to navigate and understand.
With 4 tools, the count is borderline appropriate. It feels thin for a general-purpose server, as it lacks depth in any single domain (e.g., math or user management). However, it's not extreme, so it's reasonable but could benefit from more focused scope.
There are significant gaps in the tool surface for any inferred domain. If the domain is math, tools like subtract or divide are missing; if it's user management, tools for creating or updating users are absent. The set is incomplete, leading to potential agent failures when trying to perform common operations.