SouthPow API

buy_yields_token_usdc

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

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

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 supplies important operational details itself: a $0.01 USDC charge, payment on Base or Solana, no account or API key, no charge for failed calls, live DefiLlama-sourced data, and the endpoint URL. It does not expressly state that the call is read-only with respect to DeFi positions or describe freshness and rate-limit behavior, so it is informative but not exhaustive.

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 compact passage front-loads paid status and purpose, then supplies cost, payment networks, access requirements, failure billing, and the URL. Nearly every fragment contributes distinct selection or invocation information, and the telegraphic style does not materially impair clarity.

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 three-filter lookup, the description and schema collectively cover scope, source, headline metrics, sorting and filtering controls, and commercial/access requirements. Because there is no output schema, the exact row structure and precise APY/TVL field meanings remain unspecified, while explicit sibling routing would further improve selection; neither omission prevents correct invocation.

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 the schema already documents all three optional parameters, including defaults, allowed sort values, and the limit range. The description's APY/TVL wording reinforces the resource being queried but adds no parameter syntax, interactions, or filtering semantics beyond the schema.

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?

The description identifies the resource and scope: live pools holding USDC across protocols and chains, with APY and TVL from DefiLlama. This clarifies that the 'buy' prefix concerns paid data access rather than purchasing USDC or entering an investment, although it does not explicitly contrast the chain-, protocol-, top-, or stablecoin-scoped yield siblings.

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?

'Where to earn yield on USDC' provides a concrete use case, while 'across protocols and chains' indicates when this broad token-level view is appropriate. It lacks explicit when-not guidance or routing to buy_yields_chain_* or buy_yields_protocol_* tools for narrower queries.

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?