Skip to main content
Glama

TipRanks

by com.tipranks

get_all_crypto_quotes

Read-onlyIdempotent

Real-time crypto quotes: the largest coins, each with a display name.

The feed carries 4,771 coins in alphabetical order, which is far more than one
response can hold — so this returns `limit` of them ordered by market
capitalisation, largest first, and the response states how many were left out.
Pass `symbols` for specific coins, or call get_crypto_quote for a single one.

Read `note` before summarising: it says how many coins the slice covers out of
how many exist, so a "top coins" answer is not mistaken for the whole market.

`volume` on a crypto row is the source venue's own figure and is not a common
unit across coins — some rows count coins, others quote-currency turnover. It
does not rank the market and coins cannot be compared on it.

Args:
    symbols: Comma-separated coins (optional; overrides the ranked slice)
    limit: How many ranked coins to return (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many ranked coins to return (default 40, max 75). Ignored when `symbols` is given.
symbolsNoOptional comma-separated coins to return instead of the ranked slice, e.g. 'BTCUSD,ETHUSD'. Bare tickers like 'BTC' resolve to the USD pair.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral context: the 4,771-coin feed is alphabetically stored but returned by market cap, the response reports how many coins were left out, and `volume` is venue-specific and not comparable across coins. This is exactly the kind of insight annotations do not provide.

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?

Though longer than average, every sentence earns its place: the lead sentence states purpose, the next explains scaling and alternatives, then caveats about `note` and `volume` are given, and an Args section wraps up. It is well-structured and front-loaded without filler.

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 compensates by describing key response elements: display names, slice size ('note'), left-out count, and the non-comparable `volume` field. For a two-parameter, read-only list tool, this is complete enough for an agent to use correctly and avoid summarisation errors.

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?

The input schema already covers both parameters with descriptions, defaults, maximums, and interactions, so schema coverage is 100%. The description paraphrases 'symbols overrides the ranked slice' and 'limit is how many ranked coins to return,' but adds no new semantic value beyond what the schema already provides.

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 it provides real-time crypto quotes and explicitly distinguishes from the singular get_crypto_quote tool by saying 'or call get_crypto_quote for a single one.' It also differentiates by asset class and market-cap ordering, making its scope unambiguous.

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?

It gives explicit usage guidance: use `symbols` for specific coins or call get_crypto_quote for a single one, and warns to read the `note` before summarising to avoid misrepresenting the slice as the whole market. This goes beyond mere context and directly tells when to use this tool versus alternatives.

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

All TipRanks 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.8/5.0
Disambiguation3/5

Many tools have overlapping purposes, e.g. get_etf_analysis vs get_etf_forecast both provide ETF analyst consensus, get_etf_holdings vs get_etf_top_stocks both list constituents, and get_portfolio_overview vs get_portfolio_performance both return returns/performance. The detailed descriptions help, but the sheer number of similar tools creates ambiguity in selection.

Naming Consistency4/5

The set is largely consistent with a 'get_' prefix and descriptive nouns (get_stock_quotes, get_crypto_quote, get_dividend_history). Minor deviations include 'list_my_portfolios' instead of 'get_my_portfolios' and singular/plural variants like get_all_commodities_quotes vs get_commodity_quote, but the pattern remains predictable.

Tool Count1/5

With 71 tools, the count far exceeds the 50+ threshold described as an extreme mismatch. Even though the server covers a broad financial domain, such a large surface is overwhelming for an agent and includes many redundant or highly specific tools that could be consolidated.

Completeness5/5

The tool set provides comprehensive coverage of TipRanks data: quotes and historical data for all major asset classes, news, earnings and economic calendars, analyst and sentiment data, financial statements, technical analysis, options, portfolios, and screeners. There are no obvious dead ends for typical financial research tasks.

Resources