Skip to main content
Glama
Reservoir MCP

Reservoir MCP

by joshavenue

Order book: spread, depth, slippage

reservoir_orderbook
Read-onlyIdempotent

Query minute-by-minute top-20 L2 order books to retrieve mid, spread, USD depth within chosen bps, optional order-size slippage, window medians, or a full book at a given minute.

Instructions

Minute-by-minute top-20 L2 books: mid, spread, USD depth within N bps, optional slippage for an order size, medians over the window, and the full book at a given minute (max 31 days).

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": {
      "market": "<market>"
    },
    "name": "reservoir_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoReturn the full top-20 book nearest this time instead of a window.
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.
everyNoSampling of the returned series.1h
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.
marketYesMarket 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.
depth_bpsNoDepth bands in bps from mid (default [10, 50, 100]).
notional_usdNoAlso compute buy and sell slippage for a market order of this size.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds real behavioral context on top: top-20 depth cap, a 31-day maximum window, and that windowed results are medians rather than raw samples. It omits rate limits, pagination, and empty-result behavior, keeping it short of a 5.

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 resource and enumerates outputs in the order an agent would care about them. No filler, though the run-on enumeration takes a second pass to parse.

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, return values need no explanation, and the 100%-covered input schema handles parameter detail. The description supplies the key constraints (top-20, 31-day cap, median aggregation) an agent needs before calling; only sibling differentiation is left thin.

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 the schema already documents all seven parameters including formats for start/end and the enum for every. The description adds only marginal meaning, mainly that 'N bps' maps to depth bands and 'order size' to notional_usd, plus the medians-over-window aggregation semantics.

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 specific resource and payload precisely: top-20 L2 books with mid, spread, USD depth by bps, slippage, window medians, and full-book snapshots. That is enough for an agent to tell it apart from reservoir_candles or reservoir_fills, though it never names those siblings explicitly.

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 implied rather than stated: the 'medians over the window' vs 'full book at a given minute' phrasing hints at two modes of call, and '(max 31 days)' bounds the window. There is no explicit when-to-use, when-not-to-use, or routing to alternative tools.

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