SouthPow API

buy_yields_token_wbtc

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

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

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/5.0

Behavior5/5

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

With no annotations, the description itself supplies strong operational detail: each call costs $0.005 USDC on Base or Solana, no account or API key is required, and failed calls are not charged. 'Live pools' and the DefiLlama attribution clarify freshness expectations and provenance, while the data-oriented wording makes clear that this is a lookup rather than a purchase or yield-deposit transaction.

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 packs purpose, data source, price, payment networks, access requirements, failure billing, and endpoint into a short sequence with no filler. Leading with 'Paid' and then the WBTC-specific purpose makes the key cost and selection constraints immediately visible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple query with three optional filters, the description and schema together provide enough to select and invoke it: scope, core returned metrics, source, parameter constraints, cost, and access requirements. The exact response structure remains unspecified without an output schema, but the stated pool, APY, TVL, protocol, and chain coverage is sufficient for basic correct use.

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?

All three optional parameters are documented in the schema, including sort choices, row bounds, and the TVL default, so the high schema coverage establishes a baseline of 3. The description's APY/TVL wording reinforces the domain but adds no sorting, filtering-interaction, or invocation details beyond the schema.

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?

The description identifies a WBTC-specific yield-pool lookup and states that results span protocols and chains and include APY and TVL. That scope distinguishes it from the chain-, protocol-, stablecoin-, and top-level yield siblings despite the uninformative 'buy_' prefix.

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 WBTC' gives a clear task context: choose this tool for current WBTC yield opportunities rather than general price or coin data. It does not name the chain- or protocol-specific alternatives or state when not to use it, so routing guidance is not fully explicit.

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?