Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_yearn-finance

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

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_yearn-finance"
  }
}

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.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does a solid job: it discloses the paid nature ($0.002 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and pagination behavior, but the commercial and auth model — the highest-stakes unknowns for a paid tool — are stated up front.

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?

Sentences are short and front-loaded, opening with 'Paid.' so the cost signal is impossible to miss, followed by what the data is, the price, auth requirements, and the endpoint. The trailing bare URL is slightly abrupt but functionally useful.

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, parameter-light data endpoint with no output schema, the description covers the essentials: data source, return fields, cost, payment chains, and no-charge-on-failure. It could say more about response shape and row limits, but nothing critical to invoking the tool correctly is missing.

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 in the schema. The description adds nothing parameter-specific, though listing APY and TVL as returned fields implicitly signals what sort targets exist. Baseline 3 is appropriate when the schema does the work.

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 the resource (yearn-finance pools across chains) and the fields returned (APY, TVL, 7d APY change) with the data source (DefiLlama), which is specific enough to separate it from the many buy_yields_protocol_* siblings that cover other protocols. It stops short of an explicit verb or a direct statement of how it differs from buy_yields_chain_* and buy_yields_token_*, so an agent must infer the protocol-scoped framing.

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: an agent gathers that this is the tool for yearn-finance yield data. There is no 'use this when' sentence, no exclusions, and no pointer to the chain- or token-scoped yield tools as alternatives, even though the sibling list is dominated by them.

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