Skip to main content
Glama

get_defi_yield_benchmark

Read-only

DeFi lending and stable yield benchmark from DeFiLlama Yields — top pools by APY with p25/p50/p75 APY bands, TVL, chain, and pool id. Optional protocol (project slug substring) and/or asset (symbol substring). With no filters, universe is stablecoin-marked pools (typical lending / money-market supply). Free public API, no key. $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_defi_yield_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoFilter by pool symbol substring, e.g. USDC, DAI, ETH
protocolNoFilter by DeFiLlama project slug substring, e.g. aave-v3, compound-v3

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only/safe/open-world, but the description adds context annotations cannot: data provenance (DeFiLlama Yields), no API key required, and a concrete cost of $0.02 USDC per call — a genuinely decision-relevant billing trait. It does not disclose result cardinality (how many 'top pools'), sort order, or any rate/caching behavior.

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?

Four dense sentences, front-loaded with what the tool is and what it returns, then filter behavior, then auth/cost. Telegraphic style but no filler; only the filter sentence is near-redundant with the schema.

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 carries the return-shape burden and does so by naming the returned fields and APY percentile bands. Cost and auth are covered; the notable remaining gap for a zero-required-param, no-pagination-annotated tool is how many pools constitute 'top' and whether results are truncated or sorted.

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% and both parameters already carry descriptions with examples (USDC/DAI/ETH, aave-v3/compound-v3), so the schema does the heavy lifting. The description restates the substring-matching semantics and the 'and/or' combinability of the two filters, which is mildly useful but largely duplicative — baseline 3.

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?

States a specific resource and source ("DeFi lending and stable yield benchmark from DeFiLlama Yields") plus what comes back (top pools by APY, p25/p50/p75 bands, TVL, chain, pool id). It never names or distinguishes itself against the closest-looking sibling, get_stablecoin_yield_benchmark, which is a real ambiguity given the stated default universe is stablecoin-marked pools.

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?

Gives useful call-shaping guidance: filters are optional, and with no filters the universe defaults to stablecoin-marked lending/money-market pools. That implies when the tool is appropriate, but there is no explicit when-not guidance and no routing to alternatives such as the stablecoin or yield-curve benchmarks.

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