Skip to main content
Glama

Stablecoins

stablecoins
Read-only

Stablecoins ranked by circulating supply in USD, updated daily: per stablecoin its peg type and mechanism, price, supply now and a day, a week and a month ago (in peg units), the 1d/7d/30d change and its largest chains, with the total over the selection, 50 per page. With chain, the supply, ranking and total are that chain's (stablecoin_chains ranks the chains). 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": "stablecoins"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 stablecoins per page.
chainNoA chain name as DefiLlama writes it, case-insensitive (Ethereum, Tron, Base, BSC, Solana).
peg_typeNoA peg, case-insensitive (peggedUSD, peggedEUR, peggedVAR for floating).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe read-only, non-destructive, closed-world operation, so the bar is lower; the description still adds useful behavior: daily refresh cadence, 50-per-page pagination, and the fact that the returned total is computed over the current selection. It omits default sort direction and whether the price is USD-denominated.

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 ranking scope and returned fields are front-loaded, and every clause carries information about output or scoping. The second sentence is dense and reads as a run-on, but no sentence is filler.

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?

With no output schema, the description correctly carries the burden of describing the returned fields, the aggregate total, pagination, and chain scoping, which is enough to call the tool correctly. Minor omissions (default ordering, how the 'total over the selection' behaves across pages) keep it from full completeness.

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 beyond the schema by explaining the semantic effect of 'chain' on the output (supply, ranking and total all become that chain's) rather than just restating the parameter. It adds little for 'page' beyond confirming the 50-per-page size and nothing for 'peg_type' beyond the schema's own examples.

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 opens with a specific verb+resource framing ('Stablecoins ranked by circulating supply in USD') and then enumerates the returned fields, so an agent knows exactly what the tool produces. It also explicitly distinguishes itself from the sibling 'stablecoin_chains', which ranks chains rather than stablecoins.

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 a concrete usage rule: passing 'chain' scopes supply, ranking and total to that chain, and points to 'stablecoin_chains' when chain-level ranking is the goal. It does not address when to prefer this over 'stablecoin_history' or explain what happens when no filters are supplied, so a small gap remains.

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