Skip to main content
Glama
Reservoir MCP

Reservoir MCP

by joshavenue

Who holds a perp market

reservoir_positions
Read-onlyIdempotent

Retrieve every open position in a perp market from a daily snapshot to compare long vs short accounts, notional, average entry, leverage, largest positions, liquidation prices, liquidation clusters.

Instructions

Every open position in a perp market from the daily snapshot: long vs short accounts and notional, average entry, leverage, largest positions with liquidation prices, and where liquidations cluster.

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_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many of the largest positions to list.
dateNoSnapshot day (UTC date). Default: newest snapshot.
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description usefully adds the key temporal behavior: data comes from the daily snapshot rather than live state, which is important context beyond 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?

The definition is a single front-loaded sentence that scopes the tool before enumerating the data it returns. It is dense but not padded, though part of the return-value enumeration is partly redundant given the presence of an output schema.

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?

For a read-only, annotated tool with a full input schema and output schema, the description is largely sufficient for invocation. However, it says 'perp market' while the market parameter schema explicitly includes spot markets, creating a scope mismatch that could cause the agent to skip valid use cases.

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 market, date, and top semantics. The description does not add parameter-level detail beyond indirectly implying snapshot date and largest-position limiting, so the baseline score of 3 is appropriate.

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 a specific resource and scope: open positions in a market from the daily snapshot, with long/short aggregates, entries, leverage, largest positions, and liquidation clusters. This clearly separates it from siblings like reservoir_orderbook, reservoir_fills, and reservoir_candles, though it uses no explicit verb like 'list' or 'get'.

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 by the resource: use this for position/holder data from a daily snapshot. However, it offers no explicit when-to-use or when-not-to-use guidance and does not route the agent to alternatives such as reservoir_query for custom analysis or reservoir_orderbook for live book data.

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