Skip to main content
Glama

List stablecoins with supply and peg from DefiLlama

defi_stablecoins
Read-only

Stablecoins tracked by DefiLlama: circulating supply, peg type and mechanism, price, and the chains each one runs on. With symbol, that coin; without it the 50 largest. Attribution: Data: DefiLlama. Information only, not financial advice. Related tools on this server, for a different need: defi_chains when you need total value locked by chain from DefiLlama, largest first; defi_tvl when you need total value locked in DeFi from DefiLlama. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "defi_stablecoins"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoSymbol, e.g. USDC (optional)

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
checkedAtNo
disclaimerNo
attributionNo
stablecoinsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material context beyond that, including the metered pricing model ($0.002 per successful call, failed calls not charged), the payment rail (x402, USDC on Base/Solana), and the attribution requirement. It stops short of describing result ordering or truncation behavior beyond the default-50 cap, which keeps it below a 5.

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 core capability and the parameter behavior are front-loaded in the first two clauses, with pricing and sibling routing pushed to the end where they belong. It is dense but not padded, though the sibling-routing and payment sentences make it longer than the minimal call-invocation need.

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 one-optional-parameter read tool with an output schema, an output description is unnecessary, and the definition covers the remaining agent-relevant facts: default scope, field set, cost, payment mechanism, attribution, and sibling alternatives. Nothing an agent needs to invoke it 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, but the description goes further by explaining the consequence of supplying versus omitting the optional symbol parameter (single coin versus the 50 largest). That behavioral framing of the parameter is genuinely additive rather than a restatement of the schema.

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 names a specific resource (stablecoins tracked by DefiLlama) and enumerates the returned fields: circulating supply, peg type and mechanism, price, and chains. It explicitly separates itself from defi_chains and defi_tvl, so an agent can pick the right tool without opening schemas.

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 two operating modes precisely: 'With symbol, that coin; without it the 50 largest.' It also gives explicit routing rules for the sibling tools ('defi_chains when you need total value locked by chain... defi_tvl when you need total value locked in DeFi'), which is exactly the when-to-use-versus-alternative guidance the dimension asks for.

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