Skip to main content
Glama
joshavenue

Reservoir MCP

by joshavenue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_PROFILENoAWS CLI profile to read credentials from. Use this if you want to authenticate with a named profile instead of the default AWS CLI login.default
AWS_ACCESS_KEY_IDNoAWS access key ID. Can be passed in env instead of signing in with the AWS CLI. Use together with AWS_SECRET_ACCESS_KEY.
AWS_SESSION_TOKENNoAWS session token. Optional, used together with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for temporary credentials.
RESERVOIR_AWS_CLINoFull path to aws if your app can't find it.found on PATH
RESERVOIR_DATA_DIRNoLocal copies of files, in the bucket's folder layout.~/reservoir-data
AWS_SECRET_ACCESS_KEYNoAWS secret access key. Can be passed in env instead of signing in with the AWS CLI. Use together with AWS_ACCESS_KEY_ID.
RESERVOIR_QUERY_TIMEOUT_SNoStop a query after this many seconds.300
RESERVOIR_CACHE_MAX_FILE_MBNoKeep files up to this size locally after first use.32
RESERVOIR_HARD_MAX_DOWNLOAD_MBNoHighest limit a tool call may ask for.20480
RESERVOIR_DEFAULT_MAX_DOWNLOAD_MBNoPer-call download limit when a tool call doesn't set one.1024

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
reservoir_setup_checkA

Check AWS sign-in, requester-pays access to the Reservoir bucket, DuckDB, the local data folder and this month's download total. Run this first, or whenever a tool reports a credentials error.

reservoir_coverageA

Datasets, bucket paths, market naming, venues with their first and newest day, update schedule and AWS cost. With topic, says whether Reservoir holds it and, if not, which Hydromancer API endpoint does.

reservoir_list_filesA

Like aws s3 ls: the exact Parquet files for a dataset and date range, their sizes, the full-download cost and a ready read_parquet(...) snippet for reservoir_query. Lists only; downloads nothing.

reservoir_queryA

Run DuckDB SQL directly on the Reservoir bucket, exactly like the exploring-reservoir blog. Before running, estimates the download from the columns the query reads and refuses above max_download_mb. Only the Reservoir bucket and local Reservoir copies can be read. Prefer the dedicated tools for fills, candles, books and positions.

reservoir_fillsA

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.

reservoir_candlesA

OHLCV candles at any interval, rolled up from Reservoir's 1-second candles (up to 1,500 candles per call).

reservoir_orderbookA

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).

reservoir_positionsA

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.

reservoir_walletA

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.

reservoir_downloadA

Like aws s3 cp: save whole Parquet files to the local Reservoir folder (RESERVOIR_DATA_DIR, default ~/reservoir-data), keeping the bucket's folder layout. Files already there are skipped. Use for repeated analysis.

Prompts

Interactive templates invoked by user choice

NameDescription
reservoir_guideWhich Reservoir tool answers which question, costs, and when to use the Hydromancer API instead.

Resources

Contextual data attached and managed by the client

NameDescription
reservoir_guide
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions: setup, coverage, file listing, specialized market-data queries, and file downloads. The broad reservoir_query overlaps with the specialized fills/candles/orderbook/positions tools, but its description explicitly says to prefer the dedicated tools, reducing misselection risk.

Naming Consistency4/5

All tools use the consistent reservoir_ prefix and snake_case, which makes them easy to scan and group. The set mixes action-like names (list_files, setup_check, download) with resource-like names (fills, candles, orderbook), so it is not a perfect verb_noun convention, but it remains predictable.

Tool Count5/5

Ten tools is well-scoped for a specialized market-data access server. Each tool has a clear role: setup, discovery, listing, querying, specialized data views, and downloading.

Completeness5/5

The surface covers the full read-only lifecycle for this domain: credential/setup checking, dataset discovery, file listing, SQL access, common analytical queries, and local downloads. The generic reservoir_query provides an escape hatch for any dataset not covered by the specialized tools, so there are no obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources