Skip to main content
Glama

Exchange rate

exchange_rate

Fiat exchange rate from Frankfurter (ECB). No crypto. Cached for 1 hour. amount is converted locally.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes3-letter fiat code, for example EUR.
dateNoYYYY-MM-DD. Omit for the latest rate.
fromYes3-letter fiat code, for example USD.
amountNoAmount in from. Default 1.

Output Schema

NameRequiredDescriptionDefault
okNo
dateNo
rateNo
convertedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 discloses two non-obvious traits: results are cached for 1 hour (agent knows staleness bounds) and amount conversion happens locally rather than server-side. It omits error behavior for unsupported codes and whether weekend/holiday dates fall back to a prior business day.

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?

Four telegraphic sentences, each carrying distinct information: source, scope exclusion, cache policy, computation location. Zero filler and the most decision-relevant fact (fiat only) is front-loaded.

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?

An output schema exists, so return values need no explanation, and all parameters are schema-documented. Caching and data provenance are covered; the remaining gap is date semantics (non-trading days) for a tool whose 'date' parameter spans historical rates.

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 the schema already documents all four parameters, making 3 the baseline. The description adds only one semantic detail beyond the schema — that the amount conversion is performed locally — which is useful but marginal.

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 resource (fiat exchange rate) plus its data source (Frankfurter/ECB) and a scope exclusion (no crypto). The verb is only implied ('exchange rate'), and no sibling is named, but no sibling tool overlaps this capability so the boundary is unambiguous.

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 'amount is converted locally' note suggests it doubles as a converter, and 'No crypto' rules out one class of input. It never says when to prefer this over alternatives (e.g. date_math/time_convert for date arithmetic) or what prerequisites apply.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources