Skip to main content
Glama

whale-insights

by com.cryptowhaleinsights

stablecoin_history

Get daily historical stablecoin supply changes — net inflow/outflow per day over up to 180 days (use stablecoin_flows for the current snapshot) — Returns the daily historical stablecoin net-flow and total supply over the last N days (default 30, max 180). Each day is recorded once from the live DefiLlama stablecoin cycle. Cold-start days with no data are omitted. totalFlow24h is the net USD change in stablecoin supply that day (positive = expansion / inflow, negative = contraction / outflow). totalNow is the aggregate stablecoin market cap in USD at snapshot time. signal is bullish | bearish | neutral based on the 7-day net flow. Use ?days=30 to control the window. Cached 5min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of recent days to return (1–180, default 30).

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: it explains the data source (DefiLlama), caching (5min), omission of cold-start days, and the meaning of each returned field (totalFlow24h, totalNow, signal). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but could be tightened. It includes some redundancy (e.g., mentioning default twice) and the structure is adequate but not optimized for quick scanning.

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?

Given no output schema, the description explains key return fields (totalFlow24h, totalNow, signal) and data characteristics (daily, omitted cold-start days). It lacks explicit format of the response but is otherwise sufficient for a single-parameter tool.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, the description contradicts the schema by stating 'max 180' while schema says maximum is 90. This inconsistency reduces clarity. The description adds little beyond the schema, and the conflicting values harm parameter understanding.

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 description clearly states the verb 'Get' and the specific resource 'daily historical stablecoin supply changes'. It distinguishes itself from the sibling tool 'stablecoin_flows' by noting the latter is for the current snapshot, making the purpose unambiguous.

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?

The description explicitly advises when to use 'stablecoin_flows' instead ('for the current snapshot'), providing clear guidance on choosing between tools. It also specifies the data window (up to 180 days) and default/max parameters.

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

All whale-insights toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes, but there are a few pairs with overlapping boundaries (e.g., analysts_signals vs analysts_signals_all, whale_movements vs whale_movements_summary) that could cause minor confusion.

Naming Consistency4/5

Naming is predominantly snake_case and descriptive, with minor inconsistencies in plural/singular forms (e.g., 'analysts' vs 'analyst_archive'). Overall pattern is stable.

Tool Count2/5

With 55 tools, the server is quite heavy. While the scope is broad, many tools are history/monthly variants that could be combined, making the count feel inflated beyond what is ideal for a single server.

Completeness4/5

The tool set covers a wide range of crypto analytics domains (analysts, arbitrage, funding, whales, sentiment, etc.). Minor gaps exist (e.g., no direct token price endpoint), but overall it's a comprehensive surface.

Resources