SouthPow API

buy_yields_token_prime

Paid. Where to earn yield on PRIME: live pools holding PRIME across protocols and chains, APY and TVL (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/token/prime.

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

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 behavioral burden and does it well: it declares this is a paid call at $0.002 USDC on Base or Solana, that no account or API key is required, that failed calls are not charged, and it exposes the endpoint URL. It does not cover data freshness/latency, rate limits, or what the response envelope looks like, which keeps 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?

Two dense sentences with the core purpose front-loaded and the commercial terms appended. Every clause carries information (cost, chains, payment asset, no-auth, failure policy), though the telegraphic style and trailing raw URL are slightly less scannable than a structured layout would be.

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-param read-only lookup with no output schema, the description covers what the data is (pools, protocols, chains, APY, TVL), where it comes from, and the full cost/auth model. What is missing is behavioral detail on the return payload's ordering and freshness, which matters since no output schema exists.

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% and each of the three optional parameters (sort, limit, min_tvl_usd) is fully described in the schema with defaults. The description adds nothing about them, so the baseline of 3 applies - the schema does all the work here.

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?

"Where to earn yield on PRIME: live pools holding PRIME across protocols and chains, APY and TVL" names a specific resource plus the returned metrics, which distinguishes it from buy_coin_PRIME (price) and from the buy_yields_chain_*/buy_yields_protocol_* siblings (dimension-scoped rather than token-scoped). The data source (DefiLlama) is also disclosed.

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 implied rather than stated: an agent can infer this is the token-scoped yield lookup and that buy_yields_protocol_* / buy_yields_chain_* cover the protocol- and chain-scoped variants. There is no explicit "use this when... instead of..." routing, nor any guidance on prerequisites before paying.

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?