Skip to main content
Glama

Inferventis — Financial Data, News & Web MCP

by io.github.jonathanpchapman

crypto_price

Retrieves real-time price data for any cryptocurrency listed on CoinGecko. Returns the current price in any fiat currency, 24-hour percentage change, market capitalisation, and 24-hour trading volume. Supports all major cryptocurrencies including Bitcoin (BTC), Ethereum (ETH), Solana (SOL), XRP, Cardano (ADA), Dogecoin (DOGE), Polygon (MATIC), Chainlink (LINK), Avalanche (AVAX), and 10,000+ additional coins. Use crypto_price when an agent needs the full market picture for a digital asset — price, change, market cap, and volume in one call. Prefer crypto_price_lite when only the spot price and 24h change are needed and a smaller response payload is preferred. Use crypto_fx_rates (via CoinAPI) when converting a specific amount between a cryptocurrency and fiat, or between two cryptocurrencies. Do not use this tool for fiat-to-fiat currency conversion (e.g. USD to EUR) — use currency_convert instead. Do not use when historical price data for a specific past date is required — this tool returns live spot prices only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCryptocurrency name or ticker symbol. Accepts common symbols (BTC, ETH, SOL, XRP, ADA, DOGE, MATIC, LINK, AVAX) or full names (bitcoin, ethereum, solana). Case-insensitive.
currencyNoTarget fiat currency code for the price. Must be a valid ISO 4217 code. Defaults to USD. Examples: usd, eur, gbp, jpy, chf, aud, cad.
include_market_dataNoWhether to include market capitalisation and 24-hour trading volume alongside the price. Defaults to true. Set to false for a lighter response when only the price is needed.

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that data is 'real-time', returns live spot prices only (not historical), and lists the exact fields (price, 24h change, market cap, volume). It does not mention rate limits or error behavior, but that is less critical for a read-only query tool.

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 front-loaded with purpose, then details, then usage alternatives and exclusions. Every sentence earns its place; no wasted words despite being relatively long.

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?

No output schema exists, but the description explains the return values (price, change, market cap, volume). It also covers limitations (historical data, fiat-to-fiat) and clearly positions the tool relative to siblings, making it self-contained for agent decision-making.

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%, so baseline 3 applies. The description adds minor context (e.g., 'full market picture' and 'lighter response') but the schema already describes the include_market_data flag clearly. No extra syntax or format details beyond schema.

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 states a specific verb ('Retrieves') and resource ('real-time price data for any cryptocurrency listed on CoinGecko'), clearly distinguishing from siblings like crypto_price_lite and crypto_fx_rates. It names the tool's scope and key outputs.

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?

Provides explicit when-to-use guidance, naming alternatives (crypto_price_lite, crypto_fx_rates, currency_convert) and exclusions (no fiat-to-fiat, no historical data). This exceeds the calibration example.

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