SouthPow API

buy_yields_protocol_blend-pools-v2

Paid. Live DeFi yields for blend-pools-v2: 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/blend-pools-v2.

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_blend-pools-v2"
  }
}

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.9/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 behavioral burden and does so well: it discloses the $0.002 USDC price, the two accepted payment chains (Base or Solana), that no account or API key is needed, that failures are not billed, and that data comes from DefiLlama. It stops short of rate limits or pagination behavior.

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 then packs data scope, cost, auth and billing policy into a few short sentences with no filler. The middle clause ('its pools across chains with APY, TVL, 7d APY change') is slightly run-on but still readable.

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 return content, and it does: pools across chains with APY, TVL and 7d APY change. Payment and billing caveats are covered; only response shape details and sorting semantics are left implicit.

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 sort, limit and min_tvl_usd are already documented with defaults and ranges. The description adds no further meaning about parameter effects, which is acceptable but not additive.

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 for the blend-pools-v2 protocol, its pools across chains, with APY, TVL and 7d APY change from DefiLlama. That is clearly distinguishable from the chain-scoped (buy_yields_chain_*) and token-scoped (buy_yields_token_*) siblings without opening a 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 paid framing and 'no account, no API key' tell the agent the preconditions for calling, and 'failed calls not charged' removes risk of a wasted spend. However, it never says when to prefer this over a chain-level or top-level yields tool, nor what the exclusions are.

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?