Skip to main content
Glama

Stablecoin supply history

stablecoin_history
Read-only

Stablecoin supply per day for up to 3650 days. With stablecoin (a symbol such as USDT, a CoinGecko id or DefiLlama's id): its supply in peg units and USD, price and supply on chain if given. Without: every stablecoin's supply together (USD, USD pegs at par), overall or on chain. Free data from AlphaGrowth (alphagrowth.io).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stablecoin_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of daily history, counting today.
chainNoA chain name as DefiLlama writes it, case-insensitive (Ethereum, Base, Tron).
stablecoinNoA symbol (USDT), CoinGecko id (tether) or DefiLlama id; empty for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real context beyond that: the 3650-day ceiling, that USD pegs are treated at par in the aggregate, and the AlphaGrowth free-data source. It doesn't address pagination or response shape beyond naming the fields returned, but the safety profile needs no restating.

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 purpose is front-loaded in the first clause, and every subsequent phrase adds information about the two operating modes. The 'With ... Without ...' construction is dense but slightly elliptical, requiring a second pass to parse the list of returned fields.

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?

For a 3-parameter tool with no output schema, the description carries the essential return-value information (supply in peg units and USD, price, on-chain breakdown) and the data-source caveat. Daily granularity and window bounds come from the schema, and nothing critical for a correct call appears to be 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 this description earns above baseline by explaining the accepted identifier forms (symbol, CoinGecko id, DefiLlama id) and the conditional interaction between parameters — e.g. per-chain supply only appears when a coin is specified. Format details like case handling are left to 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?

The description names the specific resource (stablecoin supply per day) and the exact payload, and its with/without-stablecoin framing separates the per-coin view from the aggregate view. It stops short of distinguishing itself from the sibling 'stablecoins' or 'stablecoin_chains' tools, so an agent must infer which of those to reach for on a non-historical question.

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

Usage Guidelines4/5

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

It gives explicit conditional usage: supply 'stablecoin' for a single coin's history, omit it for the aggregate total, and add 'chain' to scope either. There are no stated exclusions against the sibling list/chains tools, which keeps it at 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources