Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_defi_yields

Scan live DeFi yields and stablecoin APYs by chain, symbol, TVL, and project; separate organic Base APY from reward emissions for yield comparison.

Instructions

Paid x402 API ($0.005 USDC on Base): Live DeFi yield & stablecoin APY scanner powered by DefiLlama; filters by chain, symbol, TVL, and separates organic Base APY from reward emissions.

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

Input Schema

NameRequiredDescriptionDefault
chainNoComma-separated chain filter (e.g. Base, Arbitrum, Ethereum, Solana)
limitNoMax pools returned (1-100, default 20)
minApyNoMinimum total APY %
minTvlNoMinimum TVL in USD (default 100000)
symbolNoAsset symbol substring filter (e.g. USDC, ETH)
projectNoProtocol slug filter (e.g. aave-v3, morpho-v1)
stablecoinNoOnly stablecoin pools
singleAssetNoOnly single-asset no-IL pools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description has to carry the whole behavioral burden, and it does disclose the key operational facts: a paid x402 endpoint costing $0.005 USDC on Base and a DefiLlama data source. It says nothing, however, about rate limits, failure modes, result freshness, or the shape of the response, which matters because there is no output schema.

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?

It is a single dense sentence that front-loads the cost and payment rail, then the data source, filtering capability, and differentiator, with no filler. It is heavy with semicolons and parentheses, but every clause carries information.

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?

For an eight-parameter read tool with no annotations and no output schema, this is only adequate. It covers pricing, provenance, filtering, and one important output distinction, but it omits the structure and pagination of results and leaves the caller to infer behavior from the schema alone.

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 baseline is 3; each of the eight parameters is already documented inline with examples. The description adds some meaning by noting that results separate organic APY from reward emissions, but this maps to no actual parameter, and it adds nothing about the semantics of minApy, minTvl, or limit beyond what the schema states.

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 gives a specific verb and resource: it scans live DeFi yields and stablecoin APYs, sourced from DefiLlama, and can filter by chain, symbol, and TVL. It also states the distinctive output feature of separating organic Base APY from reward emissions. The only gap is that it doesn't contrast itself with the sibling tools, though they cover clearly different domains.

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 only implied by the listed filters; the description never says when to choose this tool over an alternative or when it is inappropriate. It does at least signal that this is a paid call, which lets an agent decide to invoke it sparingly, but there are no explicit preconditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.