Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_katana

Paid. Live DeFi yields on Katana: top pools by TVL or APY with base/reward 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/chain/katana.

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

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.9/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 a lot: it declares the tool paid ($0.005 USDC on Base or Solana), states no account or API key is required, and notes failed calls are not charged. What it omits is response shape, rate limits, and whether results are cached or refreshed live.

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?

The payment and access constraints are front-loaded in a single dense sentence, followed by pricing and then the endpoint URL. Nothing is padded, though the trailing URL is only marginally useful to an agent choosing whether to call the tool.

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?

There is no output schema, so the description must describe the return payload, and it does so by naming base/reward APY, TVL, and 7d APY change. Combined with explicit pricing and auth-free access, an agent has nearly everything needed; only pagination and data-freshness behavior are 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%, so the schema already documents sort, limit, and min_tvl_usd with defaults. The description restates the sort dimension but adds no format, range, or interaction detail beyond what the schema provides, so the 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?

States a specific verb and resource: live DeFi yield pools on Katana, ranked by TVL or APY, with the exact returned fields (base/reward APY, TVL, 7d APY change). This clearly separates it from the many buy_coin_* and buy_tvl_katana siblings, which cover prices and chain-level TVL rather than per-pool yields.

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 only implied by the phrase 'top pools by TVL or APY', which maps to the sort parameter rather than to a decision about when to call this versus buy_tvl_katana or the buy_yields_protocol_* tools. There are no explicit exclusions, prerequisites, or alternative-routing guidance.

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