Skip to main content
Glama

banking-intelligence

by ai.ohmyfin
OverviewDiscussionsAdmin

FX Reference Rate

fx_rate
Read-only

Get the latest available reference (mid-market) exchange rate for a pair.

Rates are the official ECB euro foreign-exchange reference rates where the ECB publishes the currency; pairs whose currency the ECB does not cover (e.g. VND, NGN, PKR, KZT, MAD) fall back to a market data feed. ALWAYS check the source field before describing provenance: "ecb" = official ECB reference rate; "market" = indicative mid-market rate, NOT an ECB fixing — never call it "the ECB rate". The source_note field in the result states this explicitly. Coverage is wide (~60 currencies) but NOT universal — some currencies (e.g. CLP, COP, PEN) have no rate on file at all. When a leg is missing, the error names exactly which currency is uncovered: relay that we hold no rate rather than supplying one from your own knowledge. Non-EUR pairs are computed as cross-rates via EUR (e.g., USD/GBP = EUR/GBP / EUR/USD), so they are indicative mid-rates, not dealable/executable rates.

BOTH currencies are required. Always pass the exact pair you intend. There is no implicit default pair: a call that omits or mis-names a currency returns a "missing required argument" error rather than a silently-wrong rate. Never assume EUR/USD when the user asked about a different pair such as USD/VND.

Examples: fx_rate("EUR", "USD") fx_rate("GBP", "JPY") fx_rate("USD", "VND")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesBase currency, ISO 4217 (e.g. "USD"). The rate is quoted as units of target per 1 base.
targetYesTarget currency, ISO 4217 (e.g. "VND").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / base / description
      Added value: +"Base currency, ISO 4217 (e.g. \"USD\"). The rate is quoted as units of target per 1 base."
    • addedInput schema / properties / target / description
      Added value: +"Target currency, ISO 4217 (e.g. \"VND\")."
  2. Changed3 schema fields changed
    • removedInput schema / properties / base / default
      Removed value: -"EUR"
    • removedInput schema / properties / target / default
      Removed value: -"USD"
    • addedInput schema / required
      Added value: +[
+  "base",
+  "target"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld, but the description discloses provenance semantics ('ecb' vs 'market', never call market data 'the ECB rate'), coverage limits (~60 currencies, CLP/COP/PEN absent), the exact error behavior on a missing leg, and that cross-rates via EUR are indicative and not executable. This is rich behavioral context well beyond the annotations.

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

Conciseness4/5

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

Front-loads the core purpose in the first sentence, then layers provenance, coverage, and error handling. It is dense but earns most of its length; the 'source'/'source_note' guidance is slightly repetitive and could be tightened.

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

Completeness5/5

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

An output schema exists, so return-value explanation is not required, and the description still calls out the result fields that matter for provenance. Combined with coverage caveats, cross-rate mechanics, and error behavior, an agent has everything needed to call this correctly.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents base/target and quote orientation, so baseline is 3. The description adds meaningful semantics on top: both params mandatory, no implicit default, mis-named currencies produce a 'missing required argument' error rather than a silently-wrong rate, plus worked examples.

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

Purpose5/5

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

Specific verb + resource: 'Get the latest available reference (mid-market) exchange rate for a pair.' It also carves out a clear niche against siblings like fx_rate_history, fx_volatility and fx_timing_advisor by emphasizing the latest single snapshot. An agent can distinguish it without opening another schema.

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

Usage Guidelines4/5

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

Strong when-to-use guidance: BOTH currencies required, no implicit default pair, never assume EUR/USD, and what to do when a leg is uncovered (relay that no rate is held rather than inventing one). It does not, however, name a sibling alternative (e.g. fx_rate_history for past rates), so it stops short of explicit routing.

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

All banking-intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources