Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Currency Converter

CurrencyConverter
Read-only

Currency Converter: Currency Converter calculates foreign exchange conversions across 170+ currencies using real-time rates. Pass an amount with source and target currency codes to receive the converted total, exchange rate, both currency names and 24-hour trend direction; paid plans add 1-day to 1-year changes, 30-day stats, and hourly and 30-day 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": {
      "value": "<value>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "CurrencyConverter"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe ISO 4217 currency code to convert to
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.
fromYesThe ISO 4217 currency code to convert from
valueYesThe amount to convert
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

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations lack: a 2-credit cost, paid-plan gating of history/hourly stats, and the constraint that hourly output is live-rates-only. That is solid added context, though it says nothing about rate limits or failure behavior for invalid currency pairs.

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 dense paragraph that front-loads the core operation, then inputs, then outputs, then cost. Every sentence carries information, though the returns list ('both currency names and 24-hour trend direction') is partly redundant given an output schema exists.

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?

For a read-only conversion tool with a rich schema and an output schema, the definition covers operation, inputs, tier-gated outputs and cost. The only real gap is sibling differentiation from CurrencyRate/ExchangeRate, which matters given the crowded financial-rate family.

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?

With 100% schema description coverage, the schema already documents all six parameters precisely, including date fallback behavior and the hourly/date exclusion. The description only adds the paid-tier requirement behind history and hourly, which is marginal beyond the schema. Baseline 3 applies.

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: calculates foreign exchange conversions across 170+ currencies with real-time rates. An agent understands the operation immediately. However, siblings CurrencyRate and ExchangeRate appear to be near-duplicates, and the description does nothing to distinguish this tool from 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?

The description implies when to use it by describing the inputs ('pass an amount with source and target currency codes') and the date-based historical mode, but it never names an alternative or says when to prefer CurrencyRate or ExchangeRate. Usage is inferable rather than guided.

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