Skip to main content
Glama

Defillama

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Defi Stablecoins

defi_stablecoins
Read-onlyIdempotent

Get stablecoin market cap and distribution across blockchains. Returns supply per chain to track adoption and network preferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
showingYesNumber of stablecoins returned (max 30)
stablecoinsYes
total_stablecoinsYesTotal stablecoins tracked

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "showing": {
+      "description": "Number of stablecoins returned (max 30)",
+      "type": "integer"
+    },
+    "stablecoins": {
+      "items": {
+        "properties": {
+          "chains": {
+            "description": "Blockchains where deployed",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "circulating_mcap": {
+            "description": "Circulating market cap in USD",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Stablecoin name",
+            "type": "string"
+          },
+          "peg_mechanism": {
+            "description": "Peg mechanism description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "peg_type": {
+            "description": "Peg type (fiat, crypto, algo, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "price": {
+            "description": "Current price in USD",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "symbol": {
+            "description": "Ticker symbol",
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "symbol",
+          "chains"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_stablecoins": {
+      "description": "Total stablecoins tracked",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_stablecoins",
+    "showing",
+    "stablecoins"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds context about returning supply per chain for tracking adoption, which is consistent but not deeply informative. No contradiction.

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

Conciseness5/5

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

Two concise sentences with no redundancy. Front-loads the key action and result.

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?

For a parameterless tool with an output schema, the description fully explains what it does and what it returns. No gaps.

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?

No parameters in schema; schema coverage 100%. Description adds no parameter info but does not need to. Baseline 4 is appropriate.

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?

Explicitly states it retrieves stablecoin market cap and distribution across blockchains, with a clear verb 'Get' and resource. Differentiates from sibling tools focused on TVL or specific protocols.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., defi_chain_tvl for general TVL). Does not specify use cases or exclusion criteria.

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

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