Skip to main content
Glama

Get exchange rate

wise_get_exchange_rate
Read-only

Retrieve current, historic, or time-series mid-market exchange rates for a currency pair to support pricing, conversion, and financial analysis.

Instructions

Get the current mid-market rate for a currency pair, a historic rate at time, or a history between from and to grouped by group.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "wise_get_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoHistory end (ISO 8601 date or timestamp)
fromNoHistory start (ISO 8601 date or timestamp)
timeNoISO 8601 timestamp for a historic rate
groupNo
sourceYesSource currency (ISO 4217, e.g. EUR)
targetYesTarget currency (ISO 4217, e.g. EUR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful qualifier 'mid-market rate', signaling this is an indicative market rate rather than a customer-facing quote, but says nothing about rate freshness, caching, rate limits, or behavior on invalid/unsupported pairs.

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?

One well-formed sentence with the current-rate case front-loaded, followed by the two conditional modes. No filler, no restatement of the title, and it forms a compact decision rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of hinting at return shape, yet it never says whether a history returns a series of rate objects or what fields accompany the rate. For a read-only, open-world rate lookup with 6 params, coverage of modes is adequate but return behavior and external-API caveats are missing.

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 description coverage is 83%, so the schema already documents `source`, `target`, `from`, `to`, and `time`; the baseline is 3. The description links `from`/`to` into a history range and mentions `group`, but 'grouped by `group`' adds essentially no meaning beyond the enum values day/hour/minute, and ISO 4217 formatting is only in the schema.

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 ('Get') and resource ('mid-market rate for a currency pair') and enumerates the three modes: current, historic at `time`, and history between `from` and `to`. It is unambiguous against siblings like wise_get_quote or wise_get_balances because it is the only rate-lookup tool, though it never explicitly names a sibling to avoid.

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?

Implicitly routes the agent among the three modes by tying each to specific parameters: pass `time` for a historic rate, `from`/`to`+`group` for a history, nothing extra for the current rate. It gives no exclusions or pointers to alternatives for related tasks (e.g. quoting a conversion, which wise_get_quote likely covers).

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