Inferventis MCP Server

currency_convert

Converts a monetary amount from one currency to another using live exchange rates sourced from the Frankfurter API (European Central Bank data). Returns the converted amount, the exact exchange rate applied, and the timestamp of the rate. Supports 30+ currencies including USD, EUR, GBP, JPY, CHF, AUD, CAD, SEK, NOK, DKK, SGD, HKD, and all major ISO 4217 codes. Use currency_convert when an agent needs to convert prices, invoices, salaries, payments, or any financial figure between fiat currencies in real time with full ECB-backed rate metadata. Prefer currency_convert_lite or currency_fx_lite when only the numeric converted amount and rate are needed without metadata. Use currency_rates when the conversion must use a historical rate from a specific past date. Do not use this tool for cryptocurrency conversion — use crypto_fx_rates (amount conversion via CoinAPI) or crypto_price (spot price lookup via CoinGecko).

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	The target currency code in ISO 4217 format. Must be uppercase. Examples: EUR, JPY, CHF, SGD, HKD, SEK.
`from`	Yes	The source currency code in ISO 4217 format. Must be uppercase. Examples: USD, GBP, EUR, JPY, CHF, AUD, CAD.
`amount`	Yes	The monetary amount to convert. Must be a positive number. Decimals are supported. Example: 1500.50 to convert one thousand five hundred and fifty cents.

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the data source (Frankfurter API/ECB), the response components (converted amount, exact rate, timestamp), and the currency scope. It does not mention rate limits, error conditions, or side effects, but the main behavioral aspects are covered.

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?

The description is appropriately sized, with each sentence serving a distinct purpose: function, output, supported currencies, when to use, alternatives, and exclusions. It is front-loaded with the core purpose and avoids extraneous detail.

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

Completeness5/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 explicitly names the return values: converted amount, exact exchange rate, and timestamp. It also covers data source, supported currencies, and alternatives. For a simple three-parameter tool, the description provides complete context for an agent.

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 the baseline is 3. The description adds value by listing example currencies and clarifying that the amount is in the source currency. This complements the schema's parameter descriptions and provides additional context beyond field names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Converts a monetary amount from one currency to another using live exchange rates.' It clearly distinguishes from siblings by naming currency_convert_lite, currency_fx_lite, currency_rates, and crypto tools with their specific purposes.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: 'Use currency_convert when an agent needs to convert prices, invoices, salaries, payments...' It also provides direct alternatives: 'Prefer currency_convert_lite or currency_fx_lite when only the numeric converted amount...' and warns against crypto use, redirecting to appropriate tools.

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

All Inferventis MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation2/5

Multiple tools have overlapping purposes, particularly the five fiat FX tools (currency_convert, currency_convert_lite, currency_convert_open, currency_fx_lite, currency_rates) and the three crypto tools (crypto_fx_rates, crypto_price, crypto_price_lite). Although descriptions attempt to differentiate them by source or detail level, the boundaries are subtle enough that an agent could easily misselect.

Naming Consistency3/5

Tool names use a mix of noun_noun, noun_verb, and adjective_noun patterns. Some include a 'lite' suffix consistently, but others like 'finnhub_stock_quote' and 'stripe_payment_records' have vendor prefixes, while bank tools lack them. Overall, the naming is readable but lacks a single consistent pattern.

Tool Count3/5

At 20 tools, the server covers a broad scope (finance, news, web, timezone) but includes redundancy (e.g., five FX conversion tools, two financial calculators). The count is not excessive for a general utility server, but it feels slightly bloated due to multiple near-identical variants.

Completeness3/5

The tool set covers many common financial and informational needs, but notable gaps exist: no historical stock data, no support for non-Stripe payment processors, and no ability to initiate payments (read-only). The news sources are limited to BBC and Guardian. Some areas are over-covered while others are missing, resulting in moderate completeness.

Resources

Need Help?