whale-data

Smart Money Radar

whale_radar

Read-onlyIdempotent

Smart Money Radar: which coins have unusual whale flow right now, across 1h, 4h and 24h windows. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`summary`	No	The answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise.
`windows`	No	The ranked coins per window, keyed 1h, 4h and 24h. Each row names the coin, its dollars in the window and how that compares with the same coin trailing hours.
`building`	No	True while the ranking has not been published yet.
`available`	No	False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
`freeCoins`	No	Keyless only: the coins whose numbers come through unblurred.
`freshness`	No	How often the ranking is rebuilt.
`generatedAt`	No	When the ranking was computed.
`lockedCount`	No	Keyless only: how many coins were held back.
`blurredMagnitude`	No	Keyless only: true because dollar sizes on held-back coins are rounded away.
`lockedUnusualCount`	No	Keyless only: how many of the held-back coins are the unusual ones.

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the specific scope of 1h/4h/24h windows and the 'descriptive only' qualifier, providing useful context that goes slightly beyond the structured annotations, but it does not address other behavioral details like data freshness or filtering behavior.

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 a single, compact sentence that front-loads the tool's purpose and includes the key temporal scope and data nature. Every clause earns its place with no filler or redundancy.

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?

Given the zero-parameter schema, full annotation coverage, and presence of an output schema, the description provides all essential decision factors: what is detected, the timeframe granularity, and the read-only nature. An agent can successfully decide whether and how to invoke this tool without further clarification.

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?

The tool has zero parameters, so the description is not required to explain parameter meanings. It still enriches the tool's semantics by clarifying the time windows (1h, 4h, 24h) and the nature of the data, earning the baseline 4 for no parameters with additional context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a specific resource and action: detecting which coins have unusual whale flow right now, across 1h, 4h, and 24h windows. It distinguishes itself from many whale-related siblings by emphasizing real-time unusual flow and multi-timeframe windows, but it does not explicitly name those siblings or demarcate its scope from them.

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?

The phrase 'right now' establishes a clear temporal context for when this tool is appropriate, and 'Descriptive market data only' signals that it is for observation rather than action. However, it does not state explicit alternatives or conditions for when not to use it, so it falls short of a 5.

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

All whale-data tools Inspect

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.6/5.0

Disambiguation3/5

Many tools share the same broad purpose domains, such as market_digest vs market_overview vs market_snapshot and whale_context vs whale_profile vs whale_flow, making selection genuinely ambiguous for an agent. The long descriptions help separate them, but the sheer number of overlapping 'one-call' market and whale views still invites misselection, and whale_tape is a direct duplicate alias.

Naming Consistency4/5

Names are consistently snake_case and mostly follow a clear domain-prefix pattern: market_*, whale_*, hl_*, defi_*. Minor deviations like liquidations vs market_liquidations, liq_zones, my_access, and the deprecated whale_tape keep it from a perfect score, but the overall convention is predictable and readable.

Tool Count2/5

With 30 tools, the server exceeds the reasonable upper bound and feels heavy even for a broad data domain. Many tools could be consolidated—for instance, several one-call market summary tools and multiple whale-flow variants—without losing capability.

Completeness4/5

The tool set covers an impressively wide range of whale and market data: news, liquidations, funding, DEX activity, Hyperliquid wallets, market scans, history, and plan access. There are minor gaps such as no general price/OHLC history or per-wallet trade history beyond swaps and fills, but agents can work around these using the existing surface.

Resources

Need Help?