Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_polkadot

Paid. Live DeFi yields on Polkadot: top pools by TVL or APY with base/reward APY, TVL, 7d APY change (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/chain/polkadot.

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

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, the description carries the full burden and does well: it discloses cost and payment rails, that no auth is needed, that failed calls are not charged, and the upstream data source (DefiLlama). It omits rate limits and pagination behavior, but the billing and access model — the highest-risk unknowns for a paid tool — are covered.

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?

Front-loads 'Paid.' and then packs purpose, output fields, price, access model, billing guarantee, and endpoint into a few dense sentences with no filler. Every clause carries actionable information.

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 simple three-optional-parameter paid query tool with no output schema, the description supplies cost, data provenance, and the shape of returned rows, which is enough to call it correctly. Only rate limits and pagination remain unaddressed.

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%, so sort, limit, and min_tvl_usd are already documented in the schema. The description only echoes the sort dimension ('by TVL or APY') and adds no syntax or default details beyond what the schema provides, 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?

The description uses a specific verb and resource ('Live DeFi yields on Polkadot') and enumerates the returned fields (base/reward APY, TVL, 7d APY change). It is clearly distinguishable from the many buy_yields_chain_* siblings by naming Polkadot, though it never explicitly routes to those siblings.

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?

It states practical prerequisites (paid, $0.01 USDC on Base or Solana, no account/API key) which helps an agent decide it can call it. However, there is no explicit when-to-use versus buy_yields_top, buy_yields_protocol_*, or other chain variants, leaving the selection logic implied by the chain name alone.

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