Tanod MCP server

chainpeek: how much of a coin sits on centralised exchanges, and is it flowing in or out (cached DefiLlama data)

get_exchange_reserves

Read-onlyIdempotent

Judge selling pressure or check reserves before depositing by seeing how much of a coin sits on centralized exchanges and whether it is flowing in or out.

Instructions

chainpeek: Use when an agent must judge selling pressure or check reserves before depositing: a coin's exchange inflow or outflow. For DEX volume use get_dex_volume. Returns how much of a coin sits on centralised exchanges and whether it is flowing in or out: per exchange the amount, USD value, share and the 1, 7 and 30-day change, totals and a daily history, from Tanod's cache of DefiLlama data. Cached DefiLlama data (refreshed every few hours), never live; the wallets are the exchanges' published or labelled wallets, so a rise means coins moved into them; symbols matched exactly; an unknown asset or exchange is a 422 and a missing or over-2-day-old cache a 503 (neither charged). Typically under 1 s (a local cache read). Price: USD 0.01. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/exchange-reserves-api.html

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Length of the daily history of the total, in days (default 30, at most 90).
`asset`	Yes	Token symbol held on exchanges, e.g. BTC, ETH, USDT, USDC (case-insensitive; matched exactly, so WBTC is not BTC).
`exchanges`	No	Exchange slugs or names to include, e.g. binance-cex, okx, bybit, kucoin (default: every tracked exchange, at most 20 names).

Output Schema

TableJSON Schema

Name	Required	Description
`days`	No
`note`	No
`as_of`	No
`asset`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`reason`	No
`source`	No
`totals`	No
`history`	No
`exchanges`	No
`not_found`	No
`exchange_count`	No
`cache_age_hours`	No
`cache_refreshed_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: cached (never live, refreshed every few hours), wallet provenance (exchanges' published/labelled wallets), what a rise means, exact symbol matching, and error behavior (422 unknown asset/exchange, 503 missing/stale cache, neither charged). This is exactly the extra transparency the bar rewards.

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?

Front-loaded with the core purpose and alternative before the operational detail; the pricing/free-tier/docs tail is dense but each sentence carries information. Slightly long, but nothing is wasted for an agent deciding and invoking correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a 3-param cached-reader with an output schema: purpose, return shape, cache freshness, matching rules, error codes, latency, pricing and docs link are all present, so an agent knows what to expect and how to recover from failures.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 asset, days and exchanges. The description adds meaning beyond it: symbols matched exactly ('WBTC is not BTC'), the semantics of a rise, and what the history window represents, though it does not restate per-parameter formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('how much of a coin sits on centralised exchanges and whether it is flowing in or out') and explicitly names the sibling to avoid: 'For DEX volume use get_dex_volume.' An agent can distinguish it from get_dex_volume, get_protocol_tvl and similar reserve/flow tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('judge selling pressure or check reserves before depositing') plus a named alternative with its condition ('For DEX volume use get_dex_volume'). Also notes the prerequisite-ish paywall/free-tier limits, which shape whether to call it at all.

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

Deploy Server