Realtap

Rank Cardano tokens

list_tokens

Read-onlyIdempotent

Ranked list of Cardano native tokens traded on DEXes, for questions such as "top tokens", "biggest gainers today", "trending now" or "new pairs". Prices are in ADA and USD, volume and liquidity in ADA (24 h), market cap in USD, changes in percent. rank (default) combines market cap with pool liquidity and is the best general ordering; volume is what the site calls Trending. The answer names the floors it applied (minLiquidityAda, minHolders).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tokens"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Page number, from 1.
`sort`	No	Ordering. volume = traded volume over `period` (the site's Trending list); gainers/losers/change use the change of the USD price over `period` (24 h: change24hPct; change24hAdaPct is the change of the ADA price) and list only tokens traded in that window with 10,000 ADA or more of pool liquidity; mcap and fdv list only tokens with 10,000 ADA or more of liquidity and 100 or more holders; txns = number of trades over `period`; makers = traders of the last 24 h; new (= age ascending) lists tokens whose first pool was seen being created; trending = trades in the last hour.	rank
`limit`	No	How many tokens to return (1-50, default 10).
`order`	No	Direction. Default: descending (age: ascending, youngest first). Ignored by rank, trending, new, gainers and losers.
`query`	No	Only tokens whose ticker, name or unit starts with this text.
`period`	No	Window of the volume, txns, change, gainers and losers orderings.	24h
`minHolders`	No	Leave out tokens known to have fewer holders than this. Replaces the default floor of the ordering (100 for mcap and fdv); 0 = none.
`hideHighRisk`	No	Leave out tokens the safety screen rates as high risk.
`minLiquidityAda`	No	Leave out tokens with less pool liquidity than this many ADA (both sides of the pools). Replaces the default floor of the ordering; 0 = none.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description is free to add genuinely new context: the units of every returned field and the fact that implicit floors (minLiquidityAda, minHolders) are applied and reported back in the answer. That filtering disclosure is the kind of behavior an agent could not infer from the schema or annotations.

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?

Front-loads purpose and example questions in the first clause, then packs units and ordering semantics into short sentences with no filler. Dense but every sentence carries information; the units sentence is a compact clause list rather than prose.

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?

For a 9-parameter, no-output-schema, read-only listing tool this is close to complete: it covers units, default ordering, floor behavior, and enrichment. Minor gaps remain around pagination behavior across the 1-1000 page range and whether the response includes total counts or applied-floor metadata beyond a mention.

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%, so 3 is the baseline, but the description adds real semantic value beyond it: it explains what `rank` means (mcap × liquidity) versus `volume` (the site's Trending), and notes that minLiquidityAda/minHolders 'replace the default floor' rather than merely filter. That default-override semantics is easy to miss in the schema text alone.

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?

States a specific verb and resource ('Ranked list of Cardano native tokens traded on DEXes') and immediately grounds it in concrete user intents ('top tokens', 'biggest gainers today', 'trending now', 'new pairs'). It also implicitly separates itself from get_trending_tokens by defining `volume` as 'what the site calls Trending', so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Maps question patterns to the tool and gives an explicit ordering recommendation: '`rank` (default) combines market cap with pool liquidity and is the best general ordering'. It does not state when NOT to use it or name concrete sibling alternatives (e.g., get_token, get_market_movers), so routing to alternatives is left to inference.

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

All Realtap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?