Skip to main content
Glama

Inferventis — Financial Data, News & Web MCP

by io.github.jonathanpchapman

crypto_price_lite

Retrieves the current spot price and 24-hour change for any cryptocurrency using the CoinGecko public API. Returns price, percentage change, and a timestamp. This is a lightweight variant of crypto_price that omits extended market data (market cap, volume) — use it when only the raw price and 24h direction are needed. Prefer crypto_price when the agent also needs market capitalisation, trading volume, or richer structured output. Use crypto_fx_rates when converting a specific amount between a cryptocurrency and fiat (e.g. 'convert 0.5 BTC to USD') rather than looking up a spot price. Supports all major coins including BTC, ETH, SOL, XRP, ADA, DOGE, and 10,000+ CoinGecko-listed assets. Accepts ticker symbols (BTC, ETH) or full names (bitcoin, ethereum). Target currency defaults to USD but accepts any ISO 4217 code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinYesCryptocurrency ticker symbol (BTC, ETH, SOL) or full CoinGecko name (bitcoin, ethereum, solana). Case-insensitive.
currencyNoISO 4217 fiat currency code for the returned price. Defaults to 'usd'. Examples: usd, eur, gbp, jpy.

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 full burden and mostly succeeds. It discloses the public API source, omits extended market data, supports 10,000+ assets, accepts ticker or full names, and notes currency default. It lacks error/rate-limit details but is otherwise transparent.

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?

The description is a bit verbose but every sentence adds value — purpose, variant comparison, usage alternatives, input formats, and defaults. It is well-organized and front-loaded with the primary action.

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?

Given there is no output schema, the description sufficiently explains the return values (price, percentage change, timestamp). It also covers core usage scenarios, parameter details, and scope, making it complete for a simple price lookup tool.

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% and includes descriptions for both parameters. The description adds value by clarifying case-insensitivity, default currency, and that full names like 'bitcoin' are accepted, going beyond schema basics.

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 retrieves current spot price and 24-hour change for any cryptocurrency, naming the returned fields (price, percentage change, timestamp). It also distinguishes itself from sibling tools crypto_price and crypto_fx_rates, making the purpose unmistakable.

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?

Explicit usage guidance is provided: use crypto_price_lite when only raw price and 24h direction are needed, prefer crypto_price for extended data, and use crypto_fx_rates for currency conversion. This gives clear decision rules for the agent.

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