Skip to main content
Glama

get_fx_rate_benchmark

Read-only

Live major currency pair benchmarks — USD/EUR, USD/JPY, USD/GBP, USD/CNY, USD/CAD, USD/MXN, DXY broad TWI, carry trade spread, and weekly/monthly/YTD rate change. Source: FRED. Updated daily. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fx_rate_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, yet the description adds substantial behavior beyond them: daily update cadence, FRED as upstream source, a $0.10 USDC per-call charge under an x402 SLA, and the specific failure contract (HTTP 503 with no charge when upstream is unavailable). It also discloses a data_source provenance field with its possible values (fred_api/fred_csv/fred_mixed), which tells the agent how to interpret freshness and reliability of the response.

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

Conciseness3/5

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

The data inventory is front-loaded and useful, but the prose is padded and internally repetitive: 'Live major currency pair benchmarks', 'Updated daily', and 'Live source' triple-state freshness, and the HTTP 503 / no-charge behavior is stated twice with subtly different conditions (>50% of fields vs. generally). Tightening to one failure statement would strengthen it.

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

Completeness4/5

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

For a read-only benchmark data tool with no output schema, the description covers what is returned, where it comes from, how fresh it is, what it costs, and how it fails — enough for an agent to call it confidently. The one material omission is the meaning and effect of the base_currency parameter, which is the only input the tool takes.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter base_currency (enum USD/EUR/GBP) is never mentioned in the description, so the agent gets no explanation of what it controls. Worse, every listed pair is USD-based (USD/EUR, USD/JPY), which gives no hint about how a EUR or GBP base would alter the output; the description should have compensated for the schema gap here and does not.

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

Purpose4/5

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

The description names the resource precisely — live major currency pair benchmarks — and enumerates the exact content returned (USD/EUR, USD/JPY, USD/GBP, USD/CNY, USD/CAD, USD/MXN, DXY broad TWI, carry trade spread, and period-over-period change). That is far more specific than the name alone. It does not explicitly differentiate from nearby siblings such as get_credit_spread_benchmark or get_commodity_benchmark, but the FX framing makes the domain unambiguous.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for FX rate data, and the mention of carry trade spread and period change hints at analytical use cases. However, there is no explicit when-to-use guidance, no statement of what it should not be used for, and no named alternative for related benchmark needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources