Skip to main content
Glama

whale-insights

by com.cryptowhaleinsights
OverviewDiscussionsAdmin

stablecoin_history

Read-onlyIdempotent

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. — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
totalNo
historyNo
updatedAtNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "days": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Snapshot date (YYYY-MM-DD, UTC).",
+            "format": "date",
+            "type": "string"
+          },
+          "signal": {
+            "enum": [
+              "bullish",
+              "bearish",
+              "neutral"
+            ],
+            "type": "string"
+          },
+          "totalFlow24h": {
+            "description": "Net USD change in stablecoin supply for that day. Positive = expansion.",
+            "type": "number"
+          },
+          "totalNow": {
+            "description": "Aggregate stablecoin market cap in USD at snapshot time.",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"Number of recent days to return (1–90, default 30)."New value: +"Number of recent days to return (1–180, default 30)."
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already indicate a safe read-only, idempotent operation. The description adds meaningful behavior: cold-start days are omitted, data is cached for 5 minutes, the signal is based on 7-day net flow, and totalFlow24h/totalNow semantics are defined. This far exceeds what annotations alone provide.

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 description is longer than strictly necessary, with some repetition between the opening sentence and the later 'Returns...' sentence. However, it is logically organized and every substantive detail — data omission, signal rules, caching, sibling routing — earns its place. It is not bloated enough to warrant a 3.

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 single-parameter, read-only tool with a rich output schema and extensive annotations, the description is nearly complete. It explains return semantics, missing-data behavior, caching, and alternatives. The only completeness gap is the inconsistent max days value, which prevents a perfect score.

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?

The schema already covers the days parameter 100%, so the baseline is 3. However, the description introduces a harmful inconsistency: it says 'max 180' and 'up to 180 days', while the input schema sets maximum to 90. This conflicting guidance could cause an agent to request an invalid window, making the description misleading rather than helpful.

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 starts with a clear verb and resource: 'Get daily historical stablecoin supply changes.' It explicitly distinguishes itself from stablecoin_flows (current snapshot) and stablecoin_monthly (long-term trends), so an agent can identify which sibling tool to choose.

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?

Usage guidance is explicit: 'use stablecoin_flows for the current snapshot', 'Use this for daily historical data', and 'use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.' It tells the agent exactly when to choose this tool over named alternatives.

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources