SouthPow API

buy_yields_token_susde

Paid. Where to earn yield on SUSDE: live pools holding SUSDE 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/susde.

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

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 supplied, the description carries the full burden and does real work: it discloses pay-per-call pricing ($0.005 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that the data is live DefiLlama data. Gaps remain on rate limits and response shape/pagination behavior, which matter for an agent that may retry or page.

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?

Two tight sentences, front-loaded with 'Paid.' so the agent learns the cost implication before anything else, then purpose, then access mechanics, then endpoint URL. Nothing is repeated and no sentence is 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?

For a zero-required-parameter paid query tool with no output schema, the description covers cost, payment rails, auth, failure billing, data source and scope. The one material omission is the return shape (fields per pool row beyond APY/TVL), which an agent would want since no output schema exists to describe it.

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 documented inline with defaults, so the baseline is 3. The description adds only indirect value by mentioning 'APY and TVL', which hints at the sort options but adds no format or constraint detail 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?

Specific verb and resource: 'Where to earn yield on SUSDE: live pools holding SUSDE across protocols and chains, APY and TVL'. It names the data source (DefiLlama) and the scope (cross-protocol, cross-chain), which cleanly separates it from the single-chain buy_yields_chain_* and single-protocol buy_yields_protocol_* siblings without opening their schemas.

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 by the scope statement rather than stated: an agent can infer this is the aggregator to call when it wants every pool for SUSDE rather than one chain or one protocol. There is no explicit 'use this instead of X when Y' routing, and no exclusions, which leaves the sibling-selection decision to inference.

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?