Exchange Rate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXCHANGE_RATE_API_KEY | Yes | Your ExchangeRate-API key (free tier available from https://exchangerate-api.com/) |
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 |
|---|---|
| convert_currencyB | Convert an amount from one currency to another using current exchange rates. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'convert_currency' follows a clear verb_noun pattern.
A single tool for an exchange rate server feels thin and limited in scope. While it covers the core conversion functionality, it lacks supporting operations like fetching available currencies, historical rates, or batch conversions, which are typical for such domains.
The tool surface is severely incomplete for an exchange rate domain. It only provides currency conversion, missing essential features like listing supported currencies, retrieving exchange rate data, or handling historical queries, which are common in financial APIs.