Skip to main content
Glama

Caelara Labs On-Chain Intelligence

stablecoin_depeg_monitor

Peg deviation in basis points for major stablecoins from independent exchange feeds

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden, yet it only discloses units (basis points) and the source class (independent exchange feeds). It says nothing about data freshness, snapshot vs streaming behavior, failure modes if a peg feed is unavailable, or rate limits – all material for a monitoring-style tool.

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?

One tight sentence fragment with no filler, and the metric and scope are front-loaded. It loses a point only because the phrasing is a bare noun phrase rather than a clause that states what the tool actually does.

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?

This is a simple read tool with one optional parameter, but there is no output schema, so the description should have sketched the return shape (per-symbol bps values, sign convention for depeg direction) and it does not. Adequate to identify the tool, insufficient to predict the response.

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 description coverage is 100%: the single optional 'symbols' parameter already documents the comma list, the allowed values (USDT, USDC, DAI), and the default of all. The description adds nothing beyond the schema, 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 metric (peg deviation in basis points) for a specific resource class (major stablecoins) and a source qualifier (independent exchange feeds), which separates it from a generic price tool like token_price_aggregator. It is a noun phrase with no verb, so the agent must infer that this is a read/retrieve operation rather than an action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no reference to any alternative tool despite siblings such as token_price_aggregator that could be confused with it. The agent gets a topic but no routing rule.

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