Skip to main content
Glama

List currencies with a Bank of Israel representative rate

list_currencies

Retrieve the 14 foreign currencies with Bank of Israel official representative exchange rates against the shekel, including English/Hebrew names and quoting units; no network request.

Instructions

List the 14 foreign currencies for which the Bank of Israel publishes an official representative exchange rate (שער יציג) against the shekel, with English/Hebrew names and the quoting unit (JPY is quoted per 100, LBP per 10). No network request is made.

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": "list_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 full burden, and it does add real behavioral context: 'No network request is made' tells the agent this is a static, side-effect-free lookup that cannot fail on connectivity, and the quoting-unit caveats (JPY per 100, LBP per 10) preempt a common misinterpretation. It stops short of describing error behavior or exact response shape, but for a zero-parameter read there is little else at risk.

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 front-loaded sentence with no filler: the scope (which 14 currencies), the payoff (names plus quoting unit), and the key behavioral fact (no network call) all appear immediately. Every parenthetical earns its place by preventing a unit-conversion mistake.

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?

With no output schema and no annotations, the description does the necessary work by describing what comes back and the quoting convention. The only minor gap is that it does not state the exact response structure or confirm that returned currency identifiers are the inputs expected by get_rate/convert_currency.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate at the input level. It wisely spends its words on output semantics (names in two languages, quoting units) instead of restating an empty schema.

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?

The description gives a specific verb (List) and a precisely bounded resource: the 14 foreign currencies for which the Bank of Israel publishes an official representative rate. It also states the returned attributes (English/Hebrew names, quoting unit), which cleanly separates it from single-rate siblings such as get_rate or get_latest_rates without needing to name them.

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: by enumerating the supported currency set, it implicitly positions itself as a discovery/lookup tool to call before get_rate or convert_currency. There is no explicit statement of when to use this versus those alternatives, nor any exclusion guidance, so the agent must infer the routing.

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