Skip to main content
Glama

Stablecoin peg monitor

stablecoin_peg_monitor
Read-only

USD stablecoin pegs — USDC, USDT, DAI, PYUSD, USDe, FDUSD and USDS — checked against $1 across independent public sources: Kraken, Coinbase and Gemini USD order books, CoinGecko's aggregate price, and Gate's FDUSD/USDT book converted at the USDT/USD rate. For each coin: the median price, deviation from $1 in bps, a severity flag (on_peg < 25 bps, watch < 50, depeg < 200, severe_depeg beyond), how far the sources disagree, and every quote with its spread and volume. Sources that fail are listed under errors; the call fails (and is not charged) only if none answers. Costs $0.002 USDC per call.

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_peg_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinsNoStablecoins to check, any case (default all): USDC, USDT, DAI, PYUSD, USDe, FDUSD, USDS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: names every data source, explains partial-failure behavior (failed sources listed under errors, call fails and is not charged only if all sources fail), and discloses the $0.002 USDC cost. That is exactly the kind of context annotations cannot carry.

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?

Front-loaded with what is measured, then sources, then return shape, then failure semantics, then cost. Dense but every clause carries information; no filler.

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 exists, yet the description enumerates the returned fields (median price, deviation in bps, severity flag with thresholds, source disagreement, per-quote spread and volume) plus error handling and pricing — enough to call and interpret results without opening anything else.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already documents the accepted coin list. The description restates the coin set but adds nothing on format beyond the schema's 'any case' note.

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?

States a specific verb and resource — USD stablecoin pegs checked against $1 — and enumerates both the coins and the sources, so an agent can distinguish it from generic price tools like crypto_price or token_price.

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

Usage Guidelines3/5

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

Implied usage is clear (depeg surveillance) but the description never says when to prefer this over siblings such as crypto_price or order_book_aggregator, nor any exclusions. Usage is inferable rather than stated.

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