Skip to main content
Glama

fetch_exchange_rate

[Personal research only] Fetch real-time currency exchange rates between two currencies with bid/ask prices and conversion rates.

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_currency": "<from_currency>",
      "to_currency": "<to_currency>"
    },
    "name": "fetch_exchange_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_currencyYesTarget currency code (e.g., 'USD', 'EUR', 'JPY') to convert to
from_currencyYesSource currency code (e.g., 'USD', 'EUR', 'GBP') to convert from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two useful traits beyond structured data: the data is 'real-time' and the result includes bid/ask spread plus a conversion rate, and it flags a personal-research-only usage restriction. It is silent on data source, rate limits, error behavior, or freshness guarantees, leaving meaningful gaps for a zero-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no filler; the what-it-does and what-it-returns are packed efficiently. The bracketed restriction is placed first, which is defensible, though the phrase itself is slightly cryptic.

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?

For a simple two-parameter tool with full schema coverage and no output schema, the description is barely sufficient: it explains the inputs only by restating them and never clarifies response shape, error cases, or whether 'real-time' implies a live quote call. It meets the minimum but could do more.

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 100%, with both from_currency and to_currency documented with examples, so the baseline is 3. The phrase 'between two currencies' only restates the schema and adds no new semantics such as case sensitivity, ISO-4217 expectations, or base/inverse handling.

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 and resource ('Fetch real-time currency exchange rates between two currencies') and even names the return payload (bid/ask prices, conversion rates). It is unambiguously distinct from the stock/company-data siblings, none of which cover FX. No explicit sibling callout, hence 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. The '[Personal research only]' tag is a licensing/scope note, not usage guidance that would help an agent decide between this and, say, fetch_quote.

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