boi-mcp

Representative rate on a date

get_rate

Fetch the Bank of Israel representative exchange rate for a currency on a given date, defaulting to today and falling back to the prior business day when no rate is published.

Instructions

Get the Bank of Israel representative rate of one currency on a given date. If no rate was published that day (weekend, holiday) the previous business day's rate is returned with is_fallback=true and days_back. Omit date for today (Asia/Jerusalem). Future dates are rejected.

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

Input Schema

Name	Required	Description	Default
`date`	No	Date in YYYY-MM-DD, e.g. 2026-10-04. Defaults to today in Israel
`currency`	Yes	ISO 4217 code such as USD, EUR, GBP, JPY (case-insensitive; symbols like $ and € also work)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist, so the description carries the burden, and it does so well by disclosing the non-obvious fallback contract (is_fallback=true, days_back) and the future-date rejection. Remaining gaps are minor: no mention of auth/rate limits or the full response shape beyond the two fallback fields.

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?

Three sentences, zero waste, front-loaded with the core purpose before the edge cases. Every sentence carries distinct information (what, fallback, date defaults/rejection).

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 two-parameter read tool with no output schema, the definition covers the edge cases an agent would realistically trip on. The only shortfall is that the primary returned rate field is never named, only the fallback metadata.

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%, so the baseline is 3; the description still adds value by restating the today-default with explicit Israel timezone and by documenting the future-date constraint, which the schema does not encode. The currency parameter gains no detail beyond the schema's ISO 4217 / symbol note.

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?

Specific verb and resource: 'Get the Bank of Israel representative rate of one currency on a given date.' The scope (single currency, single date) implicitly separates it from get_rate_history, get_latest_rates, and convert_currency, but no sibling is named, so the agent must infer the split.

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?

Gives clear operating context: omit the date to get today in Asia/Jerusalem, future dates are rejected, and weekend/holiday requests fall back. It does not explicitly say when to prefer this over get_rate_history or get_latest_rates, so the when-not guidance is incomplete.

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

Deploy Server