Skip to main content
Glama
Sign In
boi-mcp

boi-mcp

by Shtibel1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Latest Bank of Israel representative rates

get_latest_rates

Fetches official Bank of Israel representative exchange rates in ILS per unit for specified currencies or all 14, including each rate's publication date for accurate currency analysis.

Instructions

Fetch the most recent official representative exchange rates (שערים יציגים) published by the Bank of Israel, in ILS per unit. Omit currencies to get all 14. Each entry carries its own publication date (the last business day), the published rate, the quoting unit and ils_per_unit.

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_latest_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
currenciesNoOptional list of currency codes, e.g. ['USD','EUR']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it discloses the return shape (publication date on the last business day, published rate, quoting unit, ils_per_unit) and that results are official/published. It omits auth, rate-limit, and caching behavior, which keeps it from 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?

Two sentences, front-loaded with the core action and scope, then the default behavior and return fields. No filler; every clause carries information an agent needs.

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?

For a single optional-parameter read tool with no output schema, the description covers purpose, default behavior, and the fields returned. Nothing essential for correct invocation is missing.

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, but the description adds meaning the schema lacks: the default when currencies is omitted (all 14) and the ILS-per-unit output convention. That is genuine added value beyond the schema's 'Optional list of currency codes'.

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 (fetch) and resource (most recent official representative exchange rates published by the Bank of Israel), plus the unit convention (ILS per unit). The word 'most recent' implicitly separates it from the historical sibling get_rate_history, so an agent can pick correctly without opening a 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?

Gives clear operational context: 'Omit currencies to get all 14' tells the agent the default behavior and that the parameter is optional. It stops short of naming alternatives or stating when-not to use it (e.g. versus get_rate or get_rate_history), so it is clear but not exhaustive.

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

Deploy Server

Other Tools