Get live exchange rates for any currency. Sources: European Central Bank + 84 central banks, 201 currencies. No API key needed — free for commercial use.
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | Base currency code (e.g. USD, EUR, GBP). Default: EUR | |
| quotes | No | Comma-separated target currencies to filter (e.g. USD,EUR,GBP). Empty = all. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses data sources (European Central Bank + 84 central banks), number of currencies (201), and key features (no API key, commercial free). This is good but could mention rate update frequency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. Front-loaded with core purpose, then key details. Perfectly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with only 2 optional parameters and no output schema, the description provides sufficient context. It covers purpose, sources, usage conditions, and parameter defaults adequately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds context that 'quotes' empty means all currencies and base defaults to EUR, but these are already in schema descriptions. No additional meaning beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it 'gets live exchange rates for any currency', specifies sources and coverage (84 central banks, 201 currencies), and distinguishes from sibling tools like fx_get_pair_rate and fx_list_currencies by implying broad vs specific functionality.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly mentions no API key needed and free for commercial use, which helps decide when to use. However, it does not directly compare to siblings or say when not to use, though the context makes it clear this is for broad live rates.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tool groups have overlapping purposes: fda_drug_labels vs health_drug_search, fda_recalls vs health_recalls, fx_official_rates vs treasury_fx_rates, treasury_debt vs us_debt_current, and get_gdp vs get_bea_gdp. These near-duplicates create real ambiguity for an agent deciding which tool to call.
Names mix verb-led styles (get_, search_, compare_, screen_) with domain-led styles (fx_, treasury_, uk_, health_, eurostat_, datausa_). Within the same domain, similar actions use different patterns (get_gdp vs eurostat_gdp vs imf_indicator), making the set feel inconsistent and hard to predict.
75 tools is extreme for any MCP server, especially when many tools are redundant or cover unrelated domains (weather, earthquakes, scholarly search, air quality) outside the stated SEC/economics/demographics/FX focus. This overwhelms agents and burdens context windows.
Core domains like SEC financials, major economic indicators, basic demographics, and current FX rates are well covered. However, gaps remain: no historical FX rates, no stock price/quote tool, limited demographic breakdowns, and no ability to fetch full SEC filing text. Some operations end in dead ends.