Skip to main content
Glama
Reservoir MCP

Reservoir MCP

by joshavenue

Fills, volume and liquidations

reservoir_fills
Read-onlyIdempotent

Query historical Hyperliquid fills and trade metrics for a market, venue, or wallet over any date range, including volume, flow, liquidations, VWAP, and optional raw fills.

Instructions

Trades for a market, a venue or a wallet over any past window: taker volume, buy/sell split, net flow, long/short liquidations, VWAP, high/low, wallets, plus optional breakdowns and raw fills.

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

Input Schema

NameRequiredDescriptionDefault
endNoUTC. A date ("2026-10-26"), date-time ("2026-10-26T14:00:00Z"), relative ("7d", "24h") or Unix ms. A date-only end includes that whole day. Default: the newest day in Reservoir.
kindNoWhich fill file to read. liquidations/adl/twap_fills/builder_fills are much smaller than all.all
rowsNoAlso return this many individual fills (0 = none).
startNoUTC. A date ("2026-10-26"), date-time ("2026-10-26T14:00:00Z"), relative ("7d", "24h") or Unix ms. A date-only end includes that whole day. Default: the newest day in Reservoir.
venueNoVenue when no market is given (default hyperliquid).
marketNoMarket as Reservoir names it: "BTC" (Hyperliquid perp), "xyz:MSFT" (HIP-3 perp), "@107" or "PURR/USDC" (spot), "#114940" (HIP-4). Case is fixed automatically for perps. Omit to cover a whole venue.
addressNoOnly this wallet (0x...). Reservoir files are per day, so this scans whole days.
min_usdNoWith rows: only fills of at least this USD value, largest first.
group_byNoAlso return a breakdown.none
with_tx_hashNoInclude tx_hash in rows (the largest column; costs more).
max_download_mbNoStop if the estimated download is larger than this many MB (default 1024). Raise it only if the user accepts the AWS cost.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds little behavioral context of its own — the cost warnings, day-level scanning, and small-file hints all live in the schema, not the description. It does not contradict the 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?

A single front-loaded sentence that leads with scope and then lists outputs; no filler. The metrics list is dense but each clause carries information an agent needs to know the tool exists.

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 100% schema description coverage, the description only needs to convey the analytical surface, which it does by naming the aggregates and optional breakdowns/raw fills. What's missing is guidance on volume/time-range cost tradeoffs, which is relevant given a per-day file scan of possibly large downloads.

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 description coverage is 100%, so every one of the 11 parameters is already documented with format, defaults and constraints (relative dates, max_download_mb cost guard, group_by enums). The description adds no parameter-level meaning beyond the schema, which is the expected baseline at full coverage.

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?

Names a concrete resource (fills/trades) and enumerates the aggregates it returns: taker volume, buy/sell split, net flow, liquidations, VWAP, high/low, wallets, raw fills. Scope is stated as market/venue/wallet over any past window. It does not distinguish itself from siblings such as reservoir_query or reservoir_candles, so it stops short of a 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?

Usage is only implied — an agent can infer this is the fills/volume aggregation tool, but the description never says when to prefer it over reservoir_query, reservoir_candles, or reservoir_download, nor any exclusions or prerequisites. No explicit when/when-not guidance is present.

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