Skip to main content
Glama

Inferventis MCP Server

by ai.bankee

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

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

With no annotations provided, the description carries the burden and does disclose the API source, the specific return fields, and the omission of extended market data. It also notes support for 10,000+ assets and input flexibility, but lacks details on rate limits, error behavior, or timestamp format which would be useful.

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 front-loaded with the core purpose, then proceeds to variants and alternatives, and ends with input details. Every sentence adds value without redundancy.

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?

Since there is no output schema, the description appropriately specifies return values (price, percentage change, timestamp). It also covers input variety and default currency. While it doesn't mention error or edge cases, the description is sufficiently complete for the tool's simplicity.

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% and both parameters are well-documented. The description reiterates the input formats and defaults, adding minor clarity (e.g., case-insensitive, ISO 4217) but does not meaningfully expand beyond the 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 clearly states the tool retrieves current spot price and 24-hour change for any cryptocurrency via CoinGecko. It explicitly distinguishes itself as a lightweight variant of crypto_price, omitting extended market data, and names the exact output fields.

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 guidance on when to use this tool versus alternatives: use when only raw price and 24h direction are needed, prefer crypto_price for richer data, and use crypto_fx_rates for currency conversion. This is a textbook example of usage differentiation.

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 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
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