Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Exchange Rate

ExchangeRate
Read-only

Exchange Rate: Exchange Rate looks up the conversion rate between two currency codes across 170+ currencies, with both currency names and the last-updated time. Paid plans add the inverse rate, the pair's 1-day to 1-year change, its 30-day high, low, average and volatility, past dates, and hourly and 30-day daily history. (Cost: 2 credits)

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": {
      "currency1": "<currency1>",
      "currency2": "<currency2>"
    },
    "name": "ExchangeRate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional past date (YYYY-MM-DD) to use that day's closing rates instead of live rates. History runs from 1999-01-04 for about 30 major currencies and covers every supported currency from March 2024. A day with no rates, such as a weekend or holiday, uses the last close before it.
hourlyNoInclude the pair's rate for each of the last 24 hours (live rates only, not with date)
historyNoInclude the pair's daily closing rate for the last 30 days
currency1YesThe first currency you want to get the exchange rate for
currency2YesThe second currency you want to get the exchange rate for

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: coverage of 170+ currencies, inclusion of currency names and a last-updated timestamp, plan-gated feature tiers, and a stated cost of 2 credits.

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?

Purpose and scope are front-loaded in the first clause, followed by a compact enumeration of the extra data. The repeated 'Exchange Rate: Exchange Rate' opening is redundant, and the feature list is dense, but nothing else is padding.

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 an output schema present, the description need not explain return values, and it covers coverage scope, plan gating, and cost. Minor gaps remain around error behavior for invalid currency codes and whether codes must be ISO 4217, but the agent has enough to call it correctly.

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 baseline would be 3, but the description adds real meaning: it tells the agent that past dates, hourly, and 30-day history are paid-plan features, which is not stated in the schema. It does not add syntax detail beyond the schema's own examples, which is acceptable given full coverage.

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 ('looks up the conversion rate between two currency codes across 170+ currencies') and names the extra data returned (currency names, last-updated time). It does not distinguish itself from close siblings such as CurrencyRate, CurrencyConverter, or BenchmarkRate, so an agent cannot tell which of these to pick from the description alone.

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 implied by the description of what is returned and by the plan-gating note ('Paid plans add...'), which hints at when richer output is available. However, there is no explicit when-to-use or when-not-to-use guidance relative to the currency siblings, and no stated prerequisites beyond the credit cost.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources