Skip to main content
Glama

SouthPow crypto & market data

buy_yields_stablecoins

Paid. Best live stablecoin yields: stablecoin pools across all DeFi by TVL or APY (DefiLlama data). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/stablecoins.

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

Input Schema

NameRequiredDescriptionDefault
sortNotvl (default) or apy
limitNoRows, 1-100 (default 20)
min_tvl_usdNoMinimum pool TVL in USD (default 100000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well on the axes that matter for a paid endpoint: 'Paid', exact price ($0.005 USDC on Base or Solana), 'No account, no API key', and 'Failed calls not charged'. It does not cover rate limits, how payment is attached to the request, or what a response row looks like.

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?

Front-loaded with the cost signal ('Paid') and the value proposition, then pricing and access terms in tight sentences with no filler. The bare endpoint URL sits last and is arguably raw implementation detail, but it is short and plausibly aids payment/discovery.

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

Completeness3/5

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

For a three-optional-parameter query tool with no output schema, the cost/access picture is complete, but the return shape is never described — the agent cannot tell whether a row contains pool name, chain, project, TVL, APY, or reward tokens. Routing between this and the chain/protocol/token yield siblings is also unstated.

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 each parameter already documents its options and defaults (tvl/apy, 1-100 rows default 20, min TVL default 100000). The description only restates the sort dimension ('by TVL or APY') and adds no format or interaction detail, so baseline 3 applies.

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?

States a specific resource and scope: 'stablecoin pools across all DeFi by TVL or APY (DefiLlama data)'. That scope implicitly separates it from the per-chain (buy_yields_chain_*), per-protocol, and per-token yield siblings, but no sibling is named outright, so discrimination relies on the agent noticing 'across all DeFi'.

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?

Use is implied by the scope statement rather than stated: an agent can infer this is the whole-market stablecoin yield feed and the buy_yields_chain_*/buy_yields_protocol_* tools are the narrowed variants, but nothing says when to prefer one over the other. No exclusions, no prerequisites, no guidance on picking tvl vs apy sort beyond the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources