MCP Demo 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 |
|---|---|
| addC | Add two numbers together |
| greetB | Generate a personalized greeting |
| calculateC | Perform basic mathematical operations |
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 3 tools
The 'add' and 'calculate' tools have significant overlap, as 'add' is a subset of basic mathematical operations. An agent might struggle to choose between them for addition tasks, though 'greet' is clearly distinct. This ambiguity reduces clarity in the tool set.
The tools use simple verb-based names ('add', 'calculate', 'greet'), which are readable but lack a consistent pattern. There is no verb_noun structure, and while not chaotic, the naming is basic and does not follow a predictable convention across the set.
With only 3 tools, the server feels thin for a 'Demo Server' that might imply broader functionality. The count is borderline too few, as it lacks depth or variety to showcase a coherent domain, making it seem under-scoped for demonstration purposes.
Inferring a domain of basic utilities or demonstrations, the surface is incomplete. There are gaps in mathematical operations (e.g., no subtract, multiply, divide) and limited greeting functionality. This will likely cause agent failures when more complex tasks are attempted.