Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_benqi-staked-avax

Paid. Live DeFi yields for benqi-staked-avax: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/benqi-staked-avax.

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": "buy_yields_protocol_benqi-staked-avax"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNotvl (default) or apy
limitNoRows, 1-100 (default 20)
min_tvl_usdNoMinimum pool TVL in USD (default 100000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it declares the tool is paid, names the exact price and accepted payment chains, states no account/API key is required, promises failed calls are not charged, credits the data source (DefiLlama), and notes the data is live. Gaps remain around rate limits, pagination of rows, and response shape, but the commercial and data-freshness behavior is unusually well disclosed.

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?

Front-loaded with 'Paid.' followed immediately by what the tool returns, then the commercial terms, all in a compact block with no filler. The trailing URL is mildly redundant but gives a concrete endpoint, so little is wasted.

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?

No output schema exists, so the description must convey the return payload, and it does by listing APY, TVL, and 7d APY change at the pool level. Combined with full schema coverage for the three optional filters, an agent has enough to invoke it correctly; only row-count/pagination behavior for multi-chain results is unaddressed.

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 sort, limit, and min_tvl_usd are already documented with defaults and ranges in the schema. The description adds no additional semantics about these parameters (e.g., how min_tvl_usd interacts with cross-chain pools), so the baseline 3 applies.

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 (live DeFi yields for the benqi-staked-avax protocol) and enumerates the returned measures: APY, TVL, 7d APY change, sourced from DefiLlama. The 'protocol' qualifier in the name and the phrase 'its pools across chains' let an agent distinguish it from the buy_yields_chain_* and buy_yields_token_* siblings, though that differentiation is never made explicit in the text.

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?

The description supplies cost and payment logistics ($0.01 USDC on Base or Solana, no account or key, failures not charged) but never says when to choose this tool over the near-identical buy_yields_chain_* or buy_yields_token_* siblings, nor what prerequisites or filtering intent it suits. An agent must infer the selection rule from the tool name alone.

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