Skip to main content
Glama

APEX DeFi, DefiLlama & 8-Chain EVM Intel

Defi yields

defi_yields
Read-onlyIdempotent

Live DefiLlama yield pool APY and TVL rankings with chain, symbol, protocol and stablecoin filters. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
sortNotvl, apy or apyBase
chainNoe.g. Base, Ethereum, Solana
limitNo1-50
symbolNoe.g. USDC
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
projectNoe.g. aave-v3
stablecoinNotrue or false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and open-world, so the description correctly spends its words elsewhere: the $0.004 per-call cost, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-step purchase handshake. It does not say what happens when payment is absent or malformed beyond 'you get terms', and gives no rate-limit or 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool returns, then cost, then the payment procedure. No filler, no repetition of the title.

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?

For a paid, open-world read tool with no output schema, the description covers the two things an agent most needs and cannot infer: the price and the x402 payment protocol. The main remaining gap is that it never sketches the shape of the ranking response (field names such as APY, TVL, pool id), though the phrase 'APY and TVL rankings' gestures at it.

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%, so the schema already explains sort, chain, symbol, project, stablecoin and limit. The description restates the filter categories and adds only a light gloss on `payment` (the base64 PAYMENT-SIGNATURE payload), which the schema also covers. Baseline 3 is appropriate.

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 verb and resource — 'Live DefiLlama yield pool APY and TVL rankings' — plus the filter dimensions, which separates it from TVL-oriented siblings like defi_chains_tvl and defi_protocol_tvl.

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

Usage Guidelines4/5

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

It gives a clear operational sequence: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. That is real when/how guidance, but it never states when a caller should prefer a sibling tool or when this one is inappropriate.

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.