Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_solana

Paid. Live DeFi yields on Solana: 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/solana.

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

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.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that the call is paid ($0.005 USDC on Base or Solana), requires no account or API key, that failed calls are not charged, and that the data source is DefiLlama. It stops short of describing rate limits, response/pagination behavior, or what a failed/charged call looks like operationally.

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?

Telegraphic but efficient: purpose, return fields, price, payment rails, and endpoint URL each get exactly one clause with no filler. The most decision-relevant signal ('Paid') is front-loaded so an agent sees the cost implication before anything else.

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 3-optional-parameter read tool with no output schema and no annotations, the description covers the essential gaps: it enumerates the returned metrics and explains the payment model that the 'buy_' naming implies. Only minor operational details (pagination, error semantics) are absent, and the endpoint URL gives an agent a fallback path.

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 all three parameters (sort, limit, min_tvl_usd) including defaults are already documented in the schema. The description only echoes the sort dimension ('top pools by TVL or APY') and adds no syntax or constraint detail beyond that, which matches the baseline of 3.

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?

The description states a specific verb and resource ('Live DeFi yields on Solana') plus the returned fields (base/reward APY, TVL, 7d APY change) and the sort dimension, so an agent knows exactly what data comes back. It does not explicitly differentiate itself from the many sibling tools (buy_tvl_solana, buy_yields_protocol_*, other buy_yields_chain_*), relying on the tool name's chain suffix to carry that distinction.

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: an agent can infer this is the Solana-specific pool-yield endpoint and would go elsewhere for other chains or for protocol-level data. There is no explicit statement of when to prefer this over buy_tvl_solana or the buy_yields_protocol_* tools, and no exclusions or prerequisites are given beyond the payment note.

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