Skip to main content
Glama

Stablecoin supply by chain

stablecoin_chains
Read-only

Chains ranked by the stablecoins circulating on them, in USD, updated daily: per chain the total, how many stablecoins and the largest one with its share, 50 per page. stablecoins with chain lists one chain's stablecoins. 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": "stablecoin_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 50 chains per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds freshness ('updated daily'), page size ('50 per page'), return shape, and data provenance (AlphaGrowth). It does not state ordering stability beyond 'ranked' or what happens on out-of-range pages, which keeps it below 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 ranking and payload come first, then the sibling contrast and attribution, so it is well front-loaded with no filler. Minor friction from the lowercase, run-on sibling reference ('stablecoins with chain lists one chain's stablecoins'), which reads awkwardly but stays short.

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 carries the return-value burden and does so by enumerating the per-chain fields, pagination, and update cadence. Only edge-case behavior (last page, ordering ties, currency normalization) is left implicit, a small gap for a single-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one optional parameter and schema description coverage is 100%, with the schema already defining page bounds and the 50-per-page meaning. The description repeats '50 per page' but adds no new semantics such as behavior at the page ceiling or ordering guarantees, so the baseline 3 applies.

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 the resource (chains), the ranking metric (stablecoins circulating, in USD), and the per-chain payload (total, count of stablecoins, largest stablecoin and its share). It also explicitly distinguishes itself from the sibling that handles a single chain's 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 contrasts itself with 'stablecoins with chain' (one chain's stablecoins) versus this tool's cross-chain ranking, which gives the agent a clear routing rule. It stops short of an explicit 'use this when / do not use when' formulation, so it is a strong 4 rather than a 5.

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