Skip to main content
Glama

DeFi pool yields (x402)

defi_yields

Read-onlyIdempotent

$0.01 via x402: current top DeFi pools by chain/TVL, live from DefiLlama.

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
topNoHow many results to return, e.g. 10
chainNoDefault Base
min_tvlNoMinimum pool TVL in USD, e.g. 1000000
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first
stablecoin_onlyNotrue to list stablecoin pools only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the description only needs to add cost and provenance, and it does: 'live from DefiLlama' discloses the upstream source and freshness, and '$0.01 via x402' discloses a per-call charge the agent would otherwise not know about. It does not mention rate limits, what happens on payment failure, or response shape, but the payment model is the key non-obvious trait and it is surfaced.

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 sentence with no filler, but the lead position is given to the price tag rather than the capability, so the purpose arrives second. The colon-compressed phrasing is efficient yet slightly terse for an agent parsing intent.

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?

With zero required params, full schema coverage, and safety annotations present, the missing piece is guidance and outcome framing. The description says what will be listed but not what a result contains (pool, APY, TVL fields) or how the x402 payment flow resolves, which matters for a paid open-world tool with no output schema.

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 documents all five parameters, including that chain defaults to Base and how x_payment works. The description's 'by chain/TVL' merely restates two of those parameters and adds no format or edge-case detail. Baseline 3 applies when the schema does the heavy lifting.

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 resource and scope: 'current top DeFi pools by chain/TVL, live from DefiLlama.' That tells an agent it is a ranked-pool listing rather than a spread, funding, or macro tool, which separates it from most siblings. It is compressed into a single fragment, so the verb is implied ('list/get') rather than stated, and no sibling is explicitly contrasted.

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 or when-not-to-use guidance and no named alternative such as defi_vs_riskfree_spread. The word 'current' hints that it is for live snapshots rather than history, but that is inference, not guidance.

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