Skip to main content
Glama

Cumulative volume delta

cvd
Read-only

Cumulative volume delta (aggressive buys minus sells) for spot and the USDT perpetual, as in the liquidmap terminal: reset every day at 00:00 Madrid time up to 1h, every week (4h), month (1d) or year (1w).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pair": "<pair>"
    },
    "name": "cvd"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairYesCoin traded against USDT: BTC, ETH, SOL, XRP, BNB, DOGE, ZEC or NEAR
limitNoNumber of most recent points (1 to 500)
timeframeNoCandle timeframe: 1m, 5m, 15m, 1h, 4h, 1d or 1w1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=false), the description discloses the crucial behavioral trait that values reset on a fixed schedule anchored to 00:00 Madrid time, with different reset windows per timeframe. That is exactly the kind of context an agent needs to interpret the series, though it omits whether both instruments come back in one payload or how to tell them apart.

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?

A single dense sentence that front-loads the definition before the reset semantics, with no filler. The 'as in the liquidmap terminal' reference and the parenthetical timeframe/reset pairs are compressed to the point of being hard to parse on first read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explaining return values and only partially does so: it never states the unit of the delta, the point shape, or whether spot and perpetual are returned as separate series. For a read-only analytic metric with three simple parameters this is workable but leaves a real interpretive gap.

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 parameter descriptions are already handled, yet the description still adds meaning: it ties the reset window to the timeframe parameter (daily up to 1h, weekly 4h, monthly 1d, yearly 1w), which is information found nowhere in the schema. The mapping is terse and slightly cryptic, so it stops short of 5.

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 names the exact metric and defines it operationally ('aggressive buys minus sells') plus the two instruments covered (spot and USDT perpetual), so an agent knows precisely what series it gets. It does not explicitly contrast itself with siblings such as candles or big_trades, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not statement, and no alternative tool is named. The reset-window-to-timeframe mapping hints at which timeframe to pick for a given analysis horizon, but that is implied guidance rather than stated guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources