Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_stablecoin_depeg_monitor

Detect stablecoin depeg risk by tracking peg deviations in basis points for USDT, USDC, and DAI from independent market feeds.

Instructions

[On-Chain Intelligence] Peg deviation in basis points for major stablecoins from independent market data feeds Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma list from USDT,USDC,DAI (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does add genuine context - independent feed sourcing, measured p50 12 ms / p95 14 ms latency with a dated benchmark, and the backing endpoint - but it says nothing about response shape, whether all symbols are always returned, what a 'normal' versus 'depegged' value looks like, or whether any auth/rate limits apply.

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?

Two compact sentences and a category tag, front-loaded with the metric definition before the operational details. The latency benchmark is somewhat marketing-flavored but still conveys real behavioral information, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no output schema, this is close to adequate: the metric and its unit (basis points) are stated. However, with no annotations and no return schema, the description should say what comes back per symbol and whether the call is safe/read-only, and it does neither.

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?

Schema coverage is 100%: the single optional 'symbols' parameter is already fully documented in the schema with its allowed values and default. The description adds nothing about the parameter, but the schema does the work, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and metric: peg deviation in basis points for major stablecoins, sourced from independent market data feeds. That is far more informative than the tool name alone and no sibling in the list covers depeg monitoring, so confusion risk is low. It lacks an explicit verb (measure/report), which keeps it from a 5.

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?

Intended usage is implied by 'peg deviation... for major stablecoins' - an agent can infer it is for checking whether USDT/USDC/DAI have drifted off peg. There is no explicit when-to-use, no threshold guidance, and no mention of when to prefer this over the price aggregator or safety composite siblings.

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

Deploy Server

Other Tools