Tanod MCP server

chainpeek: stablecoin supply by coin and by chain with 1-day, 7-day and 30-day change (cached DefiLlama data)

get_stablecoin_supply

Read-onlyIdempotent

Fetch stablecoin supply by coin, chain, or ranking, with 1d, 7d, and 30d changes from cached DefiLlama data. Use it to size coins and chains or compare supply shifts.

Instructions

chainpeek: Get stablecoin supply by coin and chain. For whether a coin holds its peg use check_stablecoin_peg. Returns stablecoin supply by coin and chain with 1d, 7d and 30d change: a coin's chains, a chain's coins, or the largest coins and chains, from Tanod's cache of DefiLlama data. Input: optional coin, optional chain and limit; give one, both or neither. Cached DefiLlama data (refreshed every few hours), never live; as_of shows its age; an unknown name is a 422 with suggestions and a missing or over-2-day-old cache a 503 (neither charged). Informational only. Typically under 1 s (a local cache read). Price: USD 0.003. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/defi-data-api.html

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Stablecoin symbol or name, e.g. USDT, USDC, DAI, USDe, PYUSD (symbols shared by several coins return each). Omit for a chain or the overview. An unknown coin is a 422 with suggestions.
`chain`	No	Chain name, e.g. Ethereum, Tron, Solana, Base. With coin: that coin's supply on the chain. Alone: the chain's stablecoin supply and its largest coins.
`limit`	No	Rows in a ranking or a breakdown, 1-50 (default 10).

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`as_of`	No
`chain`	No
`coins`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`scope`	No
`stale`	No
`market`	No
`reason`	No
`source`	No
`top_chains`	No
`cache_age_hours`	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 read-only/idempotent/non-destructive, but the description adds far more: data is cached DefiLlama data refreshed every few hours and never live, `as_of` exposes staleness, 422 vs 503 error semantics, neither error is billed, typical latency under 1s, and pricing/free-tier limits. This is exactly the extra context the annotations cannot carry.

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 purpose and the alternative tool, then behavior, then inputs, then operational constraints. It is dense and every sentence carries information, though the leading "chainpeek:" tag and the repeated mention of cached DefiLlama data are mildly redundant against the title.

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?

An output schema exists, yet the description still sketches the return shape, and it covers staleness, error codes, billing, rate limits and a docs link. Nothing an agent needs to decide or call correctly is missing.

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 coverage is 100%, so the baseline is 3 and the schema already documents coin, chain and limit in detail. The description nevertheless adds genuine meaning beyond the schema by spelling out the combination semantics (one, both, or neither) that govern how those fields interact.

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?

The opening sentence gives a specific verb+resource ("Get stablecoin supply by coin and chain") and immediately names the sibling it must not be confused with (check_stablecoin_peg for peg status). An agent can route correctly without opening either 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?

It states the alternative tool and the condition that selects it, and it explicitly resolves the parameter-combination question ("give one, both or neither") plus what each combination returns (a coin's chains, a chain's coins, or the largest coins and chains). No usage inference is required.

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

Deploy Server