Skip to main content
Glama

Representative rate history

get_rate_history

Retrieve Bank of Israel daily representative exchange rates for a currency over a date range, with statistics and observations for historical rate analysis.

Instructions

Daily Bank of Israel representative rates for one currency over a date range (up to ~10 years). Returns count, first/last, min/max (with dates), absolute and percent change, and the observations (the most recent 400 if the range is longer; stats always cover the full range).

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>",
      "start_date": "<start_date>"
    },
    "name": "get_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYesISO 4217 code such as USD, EUR, GBP, JPY (case-insensitive; symbols like $ and € also work)
end_dateNoEnd date, YYYY-MM-DD. Defaults to today in Israel
start_dateYesStart date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the most consequential behavior: observations are truncated to the most recent 400 when the range is longer, while stats always cover the full range. That truncation rule is exactly the kind of trap an agent needs warned about. It does not mention error behavior, data availability limits, or rate/auth considerations, keeping it below a 5.

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

Conciseness5/5

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

A single sentence, front-loaded with what the tool returns, then the truncation caveat. Every clause carries information — nothing is redundant with the title or schema.

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?

There is no output schema, so the description must explain the return shape, and it does: count, first/last, min/max with dates, absolute and percent change, and observations. That is complete enough for an agent to consume the result without probing. The remaining gap is routing guidance versus sibling rate tools.

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

Parameters3/5

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

Schema coverage is 100%, so currency format, ISO codes, date patterns, and the 'defaults to today in Israel' behavior are already documented in the schema. The description adds only the ~10 year range cap, which is a real constraint but is not tied to start_date/end_date explicitly. Baseline 3 is appropriate.

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?

States a specific verb-and-resource pair: 'Daily Bank of Israel representative rates for one currency over a date range.' The scope (single currency, date range, ~10 year cap) is concrete. It does not explicitly distinguish itself from siblings such as get_rate or get_latest_rates, so it stops short of a 5.

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 only implied: the 'over a date range (up to ~10 years)' phrasing signals historical/time-series use and implies get_latest_rates is for current values, but no alternative is named and no when-not-to-use condition is stated. An agent must infer routing from sibling names alone.

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