MCP Server Demo
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sumC | Suma dos números. |
| get_exchange_rateB | Obtiene la cotización entre dos monedas. Devuelve None si hay error. |
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 have completely distinct purposes: one handles currency exchange rates, while the other performs basic arithmetic. There is no overlap or ambiguity between them.
The tools use different naming patterns: 'get_exchange_rate' follows a verb_noun convention, while 'sum' is a simple verb. This mixed approach is readable but inconsistent.
With only two tools, the server feels thin and poorly scoped. The tools (currency exchange and arithmetic) are unrelated, suggesting a lack of cohesive domain coverage.
For currency exchange, having only a 'get' operation without create/update/delete is a notable gap. For arithmetic, a single 'sum' tool lacks other basic operations like subtract or multiply, making the surface incomplete.