SouthPow API

buy_yields_protocol_accountable

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

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

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

A4/5.0

Behavior4/5

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

With no annotations, the description itself discloses the financial and operational terms: "Paid," "$0.002 USDC on Base or Solana," "No account, no API key," and "Failed calls not charged." It also identifies live DefiLlama data, but does not explicitly state read-only behavior, rate limits, or how payment is authorized.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description compactly covers purpose, metrics, provenance, pricing, payment networks, authentication, failure billing, and endpoint without unnecessary exposition. The paid nature and resource scope appear first, making the definition easy to scan.

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 simple lookup with three optional parameters, it supplies scope, source, key returned fields, endpoint, and commercial behavior while the schema covers invocation inputs. Because there are no annotations or output schema, the lack of explicit response-shape, read-only, and payment-flow details keeps it from being fully complete.

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%, and the three optional inputs already document sort values, row limits, and the minimum-TVL threshold and default. The description adds useful cross-chain pool scope but no additional parameter syntax or filtering detail, so the high-coverage baseline 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?

"Live DeFi yields for accountable" with "its pools across chains" and named metrics gives a specific data resource and protocol scope. It does not explicitly contrast this protocol endpoint with the chain, token, stablecoin, or top-yield siblings, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrases "for accountable" and "its pools across chains" make the appropriate use case clear: protocol-level yield data for Accountable across chains. There are no explicit when-not conditions or pointers to buy_yields_chain_*, buy_yields_token_*, or buy_yields_top for other scopes.

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?