Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_ethereum

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

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_ethereum"
  }
}

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
Behavior3/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 well on commerce facts: price ($0.002 USDC on Base or Solana), no account or API key required, and failed calls are not charged. It omits rate limits, pagination/response size behavior, and any freshness/latency claim beyond 'live'.

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?

Compact and front-loaded, leading with 'Paid' and then the data description before commercial terms. Minor redundancy between the leading 'Paid.' and the later '$0.002 USDC' line, and the raw URL is not strictly needed by an agent that already has the endpoint.

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 3-optional-param read tool with no output schema, the description supplies the data source (DefiLlama), the returned metrics, and the payment/auth model. Only pagination behavior and response shape beyond the listed fields remain unspecified, which is acceptable given the low complexity.

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 coverage is 100%, so the schema already documents sort, limit and min_tvl_usd with defaults. The description only echoes the TVL-vs-APY sort dimension and adds nothing about limit or the minimum-TVL filter, so 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 verb+resource with scope: 'Live DeFi yields on Ethereum: top pools by TVL or APY', plus the returned fields. The chain qualifier separates it from the other buy_yields_chain_* tools, though it never distinguishes chain-level yield listing from the buy_yields_protocol_* or buy_yields_token_* siblings.

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 can infer 'use this to see Ethereum pool yields' and that sort selects TVL vs APY ranking. There is no explicit when-not guidance and no named alternative for protocol-level or token-level yield lookups, which are heavily represented among siblings.

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