Skip to main content
Glama
ymylive
by ymylive

list_stablecoins

Get a list of stablecoins ranked by market cap with details like price, circulating supply, and optional chain distribution. Useful for comparing stablecoin sizes and tracking peg health.

Instructions

List stablecoins ranked by current circulating market cap.

Use for "what are the biggest stablecoins?", "is USDT or USDC bigger?", "where is USDC issued (which chains)?", or to track peg health (price field shows the current oracle price).

Args: limit: Number of stablecoins to return (1..200). include_chain_breakdown: If true, includes a chainCirculating map of supply per chain. If false, drops it to keep the response small (the breakdown for the top stablecoins is verbose).

Returns: Array of stablecoin summaries with id, name, symbol, pegType, pegMechanism, price, circulating, circulatingPrevDay, circulatingPrevWeek, circulatingPrevMonth, chains, and (optionally) chainCirculating. The id field is what get_stablecoin_detail would accept (DefiLlama internal id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
include_chain_breakdownNo
Behavior4/5

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

No annotations provided, but the description details return fields, conditional behavior (include_chain_breakdown), and links the id field to get_stablecoin_detail. Discloses essential behavioral traits.

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?

Well-structured with summary, examples, Args, and Returns. Front-loaded with purpose. Every sentence adds value, though could be slightly more concise.

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?

No output schema, but description thoroughly covers return fields, optional chainCirculating, and explains the id field usage. Complete for a stablecoin listing tool.

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 0%, so the description must compensate. It explains both parameters: limit (range 1-200) and include_chain_breakdown (boolean affecting response size). Adds meaning beyond schema defaults.

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 it lists stablecoins ranked by market cap, with examples like 'what are the biggest stablecoins?' Distinguishes from siblings like list_top_coins by focusing on 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?

Provides explicit use cases (e.g., comparing stablecoins, tracking peg health). Lacks explicit when not to use or alternatives, but the examples make the intent clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ymylive/coin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server