SouthPow API

buy_yields_protocol_gauntlet

Paid. Live DeFi yields for gauntlet: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/gauntlet.

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

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

Behavior5/5

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

With no annotations supplied, the description discloses the behaviors most relevant to invocation: it is paid, costs $0.005 USDC on Base or Solana, requires no account or API key, and does not charge for failed calls. It also identifies the live-data source and provides the endpoint URL, substantially reducing uncertainty around this nominally transactional 'buy' tool.

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 is compact and front-loads the paid nature before giving the data scope, metrics, source, exact price, authentication requirements, failure billing, and URL. Despite its telegraphic style, each statement supplies operationally useful information without repetition or filler.

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?

Together with the fully documented three-parameter schema, the description supplies enough scope, output-metric, pricing, authentication, and endpoint information for correct selection and invocation. Because there is no output schema, it could still be more complete about the response structure and what 'live' means for freshness, while explicit sibling routing remains absent.

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 schema already documents sort options, row limits, the minimum-TVL filter, and their defaults. The description's fixed Gauntlet and cross-chain scope is useful overall but adds little specific guidance about these parameters, so the high-coverage baseline of 3 applies.

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 the exact resource and scope: Gauntlet's DeFi pools across chains, with APY, TVL, and 7-day APY change. This protocol-specific, cross-chain scope distinguishes it from the chain-, token-, stablecoin-, and top-yield sibling tools.

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?

It provides clear selection context for an agent seeking current Gauntlet pool yields across multiple chains and cites DefiLlama as the data source. It does not explicitly route agents to chain-specific or token-specific yield siblings when those scopes would be more appropriate.

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?