Skip to main content
Glama
wesbos

Currency Converter MCP

by wesbos

get_historical_rates

Retrieve exchange rates for specific past dates to analyze currency value changes over time. Specify date, base currency, and target currencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
baseNoBase currency code (default: EUR)
symbolsNoComma-separated currency codes to limit results

Implementation Reference

  • The main tool handler function that fetches historical exchange rates from the Frankfurter API, handles parameters, makes the fetch request, and returns formatted response or error.
    export async function getHistoricalRates(
    	input: GetHistoricalRatesInput,
    ): Promise<ToolResponse> {
    	const { date, base, symbols } = input;
    
    	try {
    		const params = new URLSearchParams();
    		if (base) params.append("base", base.toUpperCase());
    		if (symbols) params.append("symbols", symbols.toUpperCase());
    
    		const url = `${FRANKFURTER_API_BASE}/${date}${params.toString() ? `?${params.toString()}` : ""}`;
    		const response = await fetch(url);
    
    		if (!response.ok) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Error: Unable to fetch historical rates. Status: ${response.status}`,
    					},
    				],
    			};
    		}
    
    		const data = (await response.json()) as ExchangeRateResponse;
    
    		return {
    			content: [
    				{
    					type: "text",
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: "text",
    					text: `Error: Failed to fetch historical rates - ${error instanceof Error ? error.message : "Unknown error"}`,
    				},
    			],
    		};
    	}
    }
  • Input schema using Zod for validating the date (YYYY-MM-DD), optional base currency (3-letter code), and optional symbols (comma-separated currencies).
    export const getHistoricalRatesSchema = {
    	date: z
    		.string()
    		.regex(/^\d{4}-\d{2}-\d{2}$/)
    		.describe("Date in YYYY-MM-DD format"),
    	base: z
    		.string()
    		.length(3)
    		.optional()
    		.describe("Base currency code (default: EUR)"),
    	symbols: z
    		.string()
    		.optional()
    		.describe("Comma-separated currency codes to limit results"),
    };
  • src/index.ts:37-41 (registration)
    Registration of the 'get_historical_rates' tool in the MCP server using the schema and handler function.
    this.server.tool(
      "get_historical_rates",
      getHistoricalRatesSchema,
      async (input) => getHistoricalRates(input),
    );
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wesbos/currency-conversion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server