Currency Exchange MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXCHANGE_API_KEY | Yes | Your ExchangeRate API key |
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 |
|---|---|
| get_exchange_rateC | Returns the current exchange rate from base to target currency. |
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 ambiguity or overlap between tools.
With a single tool, naming consistency is not a meaningful dimension; the tool name 'get_exchange_rate' follows a clear verb_noun pattern.
A single tool for a currency exchange server is too few; users likely need conversion, listing of currencies, or historical rates, making the surface feel thin.
The tool only provides current exchange rates, missing essential operations like conversion, listing supported currencies, or historical data, leaving significant gaps.