SouthPow API

buy_yields_protocol_rhea-lst

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

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_rhea-lst"
  }
}

Input Schema

Name	Required	Description
`sort`	No	tvl (default) or apy
`limit`	No	Rows, 1-100 (default 20)
`min_tvl_usd`	No	Minimum pool TVL in USD (default 100000)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations present, the description carries the burden well: it discloses the cost ($0.005 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying data source. It omits rate limits, freshness/caching behavior, and response shape, keeping it short of a 5.

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?

Terse, front-loaded fragments: what it returns, what it costs, what auth is needed, failure policy, endpoint. Nothing is padded. The telegraphic style borders on choppy but each fragment carries information an agent needs.

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, parameterless-required data query with full schema coverage and no output schema, the description supplies cost, auth model, billing failure policy, data provenance and the returned metrics. Only the response envelope and any rate/refresh limits 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%, with sort, limit and min_tvl_usd all documented in the schema including defaults, so the baseline of 3 applies. The description adds nothing about parameter behavior, though it does imply the output rows are pools with TVL and APY, which gives the filter parameters context.

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 and resource ('Live DeFi yields for rhea-lst') plus the exact fields returned (APY, TVL, 7d APY change) and the upstream source (DefiLlama). The phrase 'its pools across chains' hints at the protocol-level scope that separates it from the buy_yields_chain_* siblings, but no sibling is named explicitly.

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 reader can infer this is the right call for protocol-level rhea-lst yield data, but the description never states when to prefer it over buy_yields_chain_* or buy_yields_token_* alternatives, nor any prerequisites beyond payment. Usage is implied by the name rather than guided.

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

All SouthPow API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?