Skip to main content
Glama

Stratalize Intelligence

Get Stablecoin Yield Benchmark

get_stablecoin_yield_benchmark
Read-only

Stablecoin lending yield benchmarks — USDC/USDT/DAI supply APY across Aave, Compound, Morpho, Spark by chain. p25/p50/p75 bands, TVL filter, and spread vs 3-month T-bill. Source: DeFiLlama + FRED. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. $0.02 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": "get_stablecoin_yield_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses data provenance (DeFiLlama + FRED), liveness, the 503-with-no-charge failure mode, and a per-call price of $0.02. Cost, upstream dependency, and billing-on-failure behavior are exactly the traits annotations cannot convey, so this adds real value.

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 most decision-relevant facts (assets, protocols, metric) are front-loaded, and the cost/failure notes come last where they belong. It is telegraphic and dense — more a clause list than prose — but nearly every clause carries information.

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 does cover the return content (p25/p50/p75 bands, spread vs 3-month T-bill) and error behavior. The one gap is that 'TVL filter' has no corresponding parameter, so an agent cannot tell whether that filter is configurable or fixed server-side.

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 one parameter with 0% schema description coverage, so the description must carry the load. It names three of the four enum values (USDC/USDT/DAI) but never explains the 'all' option or what happens when the parameter is omitted (required=0). Partial compensation only.

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 verb-resource pair and enumerates the assets (USDC/USDT/DAI), the protocols (Aave, Compound, Morpho, Spark), and the metric (supply APY), so an agent knows exactly what it returns. It does not distinguish itself from the close sibling get_defi_yield_benchmark, leaving the boundary implicit.

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?

Use is implied by the content — pull this when you need stablecoin lending rates — but there is no explicit when-to-use, when-not-to-use, or named alternative. The closest sibling, get_defi_yield_benchmark, is never mentioned, so an agent must infer which to prefer.

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