LiquidVision — Crypto Derivatives Data

get_footprint

Read-onlyIdempotent

[measured] Footprint chart data: for each candle, taker BUY and taker SELL volume in USD and the trade count at each of 30 price levels, from the archived trade streams of Binance, Bybit, OKX, Bitget and Gate. Use it to see at which prices aggressive buyers or sellers were absorbed; for the net flow over time by trade size use get_cvd. symbol: BTCUSDT, ETHUSDT or SOLUSDT only. minutes: look-back window, 15 to 10080. step: candle size in minutes, 1 to 240.

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": "get_footprint"
  }
}

Input Schema

Name	Required	Description	Default
`step`	No	Candle size in minutes, 1 to 240.
`symbol`	No	Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT).	BTCUSDT
`minutes`	No	Look-back window in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / step / description

Previous value: -"Price step of the grid, in quote units."New value: +"Candle size in minutes, 1 to 240."

Changed3 schema fields changedNov 6, 2026

addedInput schema / properties / minutes / description
```
Added value: +"Look-back window in minutes."
```

addedInput schema / properties / step / description

Added value: +"Price step of the grid, in quote units."

addedInput schema / properties / symbol / description

Added value: +"Contract as BASEUSDT, e.g. BTCUSDT, ETHUSDT, SOLUSDT (1000PEPE and kPEPE fold to PEPEUSDT)."

First observedSep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, and the description adds real context beyond them: the five source exchanges, that data comes from archived trade streams, and the 30-level aggregation granularity. It does not say anything about data latency, history availability per exchange, or expected response size, which matters for a look-back window up to 10080 minutes across five venues.

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-loaded with the payload shape, then use case, then alternative, then parameter bounds — a sensible ordering with no filler sentences. The leading '[measured]' marker is unexplained and costs a little clarity, but density is otherwise high.

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 no output schema, the description carries the burden of describing return values, and it does so well by enumerating the per-candle fields and the 30-level breakdown. It stops short of mentioning candle timestamps, ordering, or how far back archived streams actually go, which an agent sizing a request against five exchanges would want.

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%, which sets the baseline at 3, but the description earns an upgrade: it narrows symbol to BTCUSDT/ETHUSDT/SOLUSDT only (the schema's generic BASEUSDT wording is broader) and supplies the minutes range of 15 to 10080, which the schema does not state at all. The step range duplicates the schema rather than adding to it.

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 ('Footprint chart data') and immediately spells out the shape of the payload: per-candle taker BUY/SELL volume in USD plus trade count across 30 price levels. It also names the sibling it is not (get_cvd) for net flow by trade size, so an agent can distinguish it from the other volume tools 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 Guidelines5/5

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

Gives an explicit use case ('see at which prices aggressive buyers or sellers were absorbed') and routes the alternative case to get_cvd with the distinguishing criterion (net flow over time by trade size). Constraints on symbol, minutes and step are stated inline, leaving little to inference.

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

All LiquidVision — Crypto Derivatives Data 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?