Skip to main content
Glama

Rate history

get_rate_history
Read-onlyIdempotent

Shows how the market exchange rate from US dollars to another currency has moved over the last 24 hours, 7 days, 30 days, 90 days or a year. It is the rate before any fees, so it is not the rate a payment is priced at, and a past series is no forecast. Use it when someone asks how a currency has moved against the dollar. Don't forecast the rate or advise when to convert, all at once or in stages, from this or any other source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "currency": "<currency>",
      "range": "<range>"
    },
    "name": "get_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful semantics beyond them: the series is the pre-fee mid-market-style rate, not a priced rate, and historical data carries no predictive guarantee. It does not mention sampling granularity per range, but that is a minor omission for a read-only lookup.

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?

Purpose and scope are front-loaded, then caveats, then usage. Every sentence carries information, though the closing admonition about staged conversion is longer than the guardrail requires.

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 simple two-parameter read-only tool with full annotation coverage and no output schema, the description supplies purpose, caveats, and usage. The only gap is that the shape of the returned series (timestamps vs. points per range) is left implicit.

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 0%, so the description must carry the load, and it does the important part: it clarifies that 'currency' is the non-USD leg ('from US dollars to another currency'), which the schema's bare string pattern cannot convey. It also enumerates all five ranges in prose, though it does not map them to the enum tokens (24h/7d/30d/90d/1y).

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?

States a specific verb and resource (historical movement of the USD exchange rate) plus the exact supported horizons. It also draws the line against the quote tools implicitly: 'It is the rate before any fees, so it is not the rate a payment is priced at.' An agent can distinguish this from get_send_quote/get_receive_quote without opening their schemas.

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?

Explicit trigger: 'Use it when someone asks how a currency has moved against the dollar,' plus a clear negative boundary (no forecasting, no conversion advice). It stops short of naming which sibling to call for a priced rate, leaving that to inference, which keeps it from a 5.

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.