Skip to main content
Glama

Inferventis — Financial Data, News & Web MCP

by io.github.jonathanpchapman

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
NameRequiredDescriptionDefault
toYesThe target currency code in ISO 4217 format. Must be uppercase. Examples: EUR, JPY, CHF, SGD, HKD, SEK.
fromYesThe source currency code in ISO 4217 format. Must be uppercase. Examples: USD, GBP, EUR, JPY, CHF, AUD, CAD.
amountYesThe 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.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the live data source, return values (converted amount, rate, timestamp), and supported currencies. It doesn't explicitly state there are no side effects or auth requirements, but as a conversion tool the read-only nature is implicitly clear. The API source and metadata details provide solid transparency.

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 well-structured and every sentence contributes value: purpose, return info, currency list, usage guidance, alternatives, and exclusions. It is front-loaded with the core function and remains appropriately sized for the decision-making needs it addresses.

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?

Despite no output schema, the description explains the return values and metadata. The tool is simple (3 params) and the description covers purpose, supported inputs, alternatives, and explicit exclusions. This is complete for an agent to select and invoke correctly.

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 parameter descriptions already provide full semantics. The tool description adds minimal parameter-specific value beyond reiterating currency support and examples; it doesn't clarify parameters beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool's function: converting a monetary amount between currencies using live exchange rates. It identifies the specific resource (Frankfurter API/ECB data) and distinguishes from sibling tools by naming alternatives like currency_convert_lite, currency_fx_lite, and currency_rates.

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?

Explicitly provides when-to-use guidance for full metadata needs, and when to prefer lite versions for just amount/rate. Also directs users to currency_rates for historical rates and warns against crypto conversions, naming the appropriate tools. This is comprehensive alternative selection guidance.

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

All Inferventis — Financial Data, News & Web MCP toolsInspect
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
Disambiguation3/5

Many tools have overlapping purposes, especially in currency conversion (5 tools) and financial calculations (2 tools). While descriptions are detailed and try to differentiate, the sheer number of similar tools could confuse an agent. The platform_tool_finder tool helps but doesn't fully resolve ambiguity.

Naming Consistency3/5

Naming follows snake_case but is inconsistent: some tools use noun_verb (e.g., currency_convert), others noun_noun (e.g., bank_accounts). There are also variants with suffixes like '_lite' and '_open' which help, but the pattern varies across the set.

Tool Count4/5

20 tools is reasonable for a financial data and news server, covering stocks, crypto, fiat, banking, payments, calculations, and web content. However, there is redundancy (5 fiat converters) that could be streamlined, making the count slightly higher than ideal.

Completeness4/5

The tool set covers a broad range of financial tasks: real-time stocks, crypto, fiat conversion, bank transactions, payments, financial calculations, news, and web reading. Minor gaps exist, such as lack of historical stock data or portfolio tracking, but most common queries can be handled.

Resources