Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_op-mainnet

Paid. Live DeFi yields on OP Mainnet: top pools by TVL or APY with base/reward 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/chain/op-mainnet.

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_chain_op-mainnet"
  }
}

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

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

With no annotations at all, the description carries the full burden and does well: it discloses the cost ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that data comes from DefiLlama. Gaps remain on rate limits, pagination, and what a successful paid response envelope looks like.

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-loads 'Paid.' and the core capability, then packs pricing, auth, and failure terms into a dense block with no filler. The telegraphic fragments and trailing raw URL are slightly rough but each clause carries information.

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 three-optional-parameter read tool with no output schema and no annotations, the description covers purpose, data source, returned metrics, cost, and payment mechanics — enough to call it confidently. Only the response shape and pagination behavior are left unstated.

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 defaults and ranges for sort, limit, and min_tvl_usd are already documented. The description's mention of 'top pools by TVL or APY' only restates the sort parameter and adds no format or interaction detail beyond the schema.

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?

States a specific verb and resource — 'Live DeFi yields on OP Mainnet' — plus the exact scope (top pools ranked by TVL or APY) and the fields returned (base/reward APY, TVL, 7d APY change). Combined with the chain-specific name, an agent can distinguish it from the dozens of sibling buy_yields_chain_* and buy_tvl_* tools without opening the schema.

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?

The commercial context ('Paid', price, accepted payment chains, failed calls not charged) is clear, but there is no explicit statement of when to prefer this over buy_tvl_op-mainnet or the per-protocol buy_yields_protocol_* tools. Usage is only implied by the chain+pool framing.

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