Skip to main content
Glama
Reservoir MCP

Reservoir MCP

by joshavenue

One wallet's daily snapshot

reservoir_wallet
Read-onlyIdempotent

Retrieve a wallet's perp positions, spot balances, and account values from global snapshots for a chosen day; optionally limit parts and download size.

Instructions

A wallet's perp positions, spot balances and account values on a given day, from the global snapshots. These files are not split by wallet, so each part scans the whole day's file.

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": {
      "address": "<address>"
    },
    "name": "reservoir_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoSnapshot day (UTC date). Default: newest snapshot.
addressYesWallet address, 0x followed by 40 hex characters.
includeNoParts to read (default all three).
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.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds a genuinely useful non-obvious trait: the underlying files are not partitioned by wallet, so each requested part scans the full day's file — a real cost/latency signal that pairs with the schema's max_download_mb guard.

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?

Two sentences, front-loaded with the concrete payload and followed by the operational caveat; nothing is wasted. The second sentence is terse to the point of slight ambiguity about what 'these files' refers to, keeping it just short of a 5.

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% param coverage, the description need only frame scope and cost, which it does. The main remaining gap is routing guidance against reservoir_positions/reservoir_query, which an agent would need to choose this tool correctly.

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 explains date defaulting, address format, the include enum, and the download cap; baseline 3 applies. The description only indirectly motivates 'include' via the whole-file scan note and adds no format or default detail beyond the schema.

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 the specific resource (perp positions, spot balances, account values for one wallet on one day) and the source (global snapshots), which is concrete enough to distinguish it from a generic query tool. It does not explicitly name reservoir_positions or reservoir_query as the alternative, so sibling differentiation is only implied.

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 'one wallet's daily snapshot' versus the whole-day global files, but there is no explicit when-to-use statement, no exclusion of reservoir_positions or reservoir_query, and no prerequisites (e.g. needing reservoir_setup_check first). The agent must infer selection from the name and the one-line scan caveat.

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