whale-data

One-call trade context

trade_context

Read-onlyIdempotent

The pre-trade context blob in one call: price, cross-venue funding with time-to-next-funding and carry arithmetic (optional position_usd), open interest, whale flow vs the coin's own baseline, and recent visible liquidations, on ANY streamed pair keyless. compact: true returns the one-line composed answer (about 30 tokens). A paid developer plan adds the percentile judgment vs the pair's own recorded days, whale USD magnitudes, full 24h stats and the crowding score. Strictly descriptive: state plus recorded history, no advice. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Alias for pair.
`pair`	No	Trading pair, for example ETH/USD. A bare symbol like ETH is read as ETH/USD. Defaults to BTC/USD when omitted. Any streamed pair answers keyless; off the free pairs a keyless reply is the lite shape and names what it withheld in locked_layers.
`compact`	No	Return one line of plain text rather than the JSON blob, about 30 tokens instead of 800. Same facts, same windows, same dates, no structured fields to read. Defaults to false.
`position_usd`	No	Position size in US dollars, for example 25000. Above zero only. When given, carry_cost adds per_day_usd_at_current_rate, the dollars a day the current funding average across exchanges works out to at that size. Arithmetic on the rate as it stands now, not a projection of future rates. Omit and carry_cost still carries the percentage and APR figures.

Output Schema

TableJSON Schema

Name	Required	Description
`line`	No	The composed one-line answer, returned only when compact:true was asked for. The same facts, the same windows and the same dates as the full shape.
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`pair`	No	The pair this context describes.
`depth`	No	Which shape came back: lite, free-pair or keyed.
`price`	No	Last traded price.
`compact`	No	Present and true only on a compact:true call, where the whole answer is the single line in `line`.
`funding`	No	average_rate across exchanges, how many exchanges are in it, the interval in hours, and minutes to the next funding time.
`crowding`	No	The crowding read and the overexposed side. Null without a developer plan.
`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.
`stats_24h`	No	The 24h statistics block. Absent on the lite shape, where locked_layers names it.
`carry_cost`	No	Arithmetic on the current funding average: percent per day, the same as an annual rate, which side pays, and dollars a day when position_usd was passed. Not a projection of future rates.
`whale_flow`	No	Whale direction against the same coin logged baseline: the multiple, days logged, record and N-day-high flags, and buy share now versus 7 days. Dollar sizes are added on a developer plan.
`locked_layers`	No	Named rather than silently missing: which blocks this connection did not receive.
`vs_own_history`	No	Where funding and open interest sit against the same pair recorded days: phrase, band, day count, the date the reading is from, and how past cases resolved.
`open_interest_usd`	No	Open interest in dollars across the exchanges that publish it.
`liquidations_recent`	No	Forced closes visible right now: count, long_usd, short_usd and window_minutes. A timing series, market-wide totals run higher.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context: compact mode returns a one-liner instead of JSON, paid plan gates advanced analytics, and it explicitly states 'Strictly descriptive: state plus recorded history, no advice.' This goes beyond annotations, though some behaviors like locked_layers are only in the schema.

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 dense but well-structured: starts with the core purpose, then lists components, then options (compact), then paid plan, then disclaimers. Each sentence adds information, though it is somewhat long and could be tightened without losing content.

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?

With an output schema present and annotations covering safety, the description covers the main data components, the compact alternative, paid vs free limitations, and the descriptive nature. It is quite complete for a complex composite tool, though it could better explain free vs paid data shape (e.g., locked_layers) directly in the description.

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 coverage is 100%, so the baseline is 3. The description mentions position_usd in the context of carry arithmetic and compact, but these are also covered in the schema details. It does not add significant new meaning 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 the tool returns a pre-trade context blob with specific components (price, funding, open interest, whale flow, liquidations) on any streamed pair keyless. This distinguishes it from specialized siblings like funding_matrix or whale_flow, and the title 'One-call trade context' reinforces its purpose.

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 'pre-trade context blob in one call' indicates when to use it (broad pre-trade overview), and the schema adds keyless vs paid usage context. However, it does not explicitly mention alternative tools or when not to use this tool, so it lacks explicit exclusions.

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?