Skip to main content
Glama

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

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds materially beyond them: upstream sources (DeFiLlama + FRED), liveness, the exact failure mode (HTTP 503 with no charge when >50% of fields are unavailable), and the per-call price. Cost and error semantics are precisely the behavioral facts an agent needs before invoking a paid, network-dependent 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?

Dense, front-loaded fragments with no filler: scope first, then metrics, then provenance, then failure and pricing. The telegraphic style ('Live source.') costs a little clarity, but every clause carries information an agent can act on.

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 still conveys the returned measures (p25/p50/p75 bands, spread vs 3-month T-bill) and the TVL filter, plus source, freshness, and failure behavior. The remaining gap is response behavior for the omitted 'all' option and default parameter handling.

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 optional parameter with an enum and 0% schema description coverage. The description names three of the four enum values (USDC/USDT/DAI) but never mentions 'all', does not say the parameter is optional, and does not state what the default or 'all' behavior returns, so it only partially compensates for the coverage gap.

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 a specific resource and enumerates its scope: stablecoin supply APY for USDC/USDT/DAI across Aave, Compound, Morpho, and Spark, segmented by chain. That enumerated asset class plus protocol list is enough to separate it from the general 'get_defi_yield_benchmark' and from 'get_yield_curve_benchmark' without opening either schema.

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?

Usage is implied by the scope — an agent can infer this is for benchmarking stablecoin lending rates — but there is no explicit when-to-use, when-not, or named alternative. Nothing tells the caller whether to prefer this over the broader DeFi yield sibling when both could answer.

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