Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_pancakeswap-amm

Paid. Live DeFi yields for pancakeswap-amm: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/pancakeswap-amm.

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_protocol_pancakeswap-amm"
  }
}

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.7/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 behavioral load and does it well for a paid endpoint: it discloses the $0.002 USDC cost, payable on Base or Solana, no account or API key required, no charge on failed calls, and DefiLlama as the data source. It stops short of rate limits, pagination behavior, or what an empty result 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 "Paid" and the resource, then compresses output fields, price, and access constraints into two tight sentences. The trailing raw endpoint URL is the only weakly-earning element, and "Paid." slightly duplicates the price sentence.

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-param, no-output-schema tool, the description covers what is returned (APY, TVL, 7d APY change), the data source, the chain scope, and the payment model, which is enough for an agent to call it correctly. Missing only result-size/pagination expectations, which is a minor gap.

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%, with sort (tvl/apy), limit (1-100, default 20) and min_tvl_usd (default 100000) all documented inline, so the schema does the heavy lifting. The description adds no parameter-level meaning (e.g. how sort interacts with min_tvl_usd filtering), 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?

"Live DeFi yields for pancakeswap-amm: its pools across chains with APY, TVL, 7d APY change" states a specific resource (PancakeSwap AMM pool yields) plus the fields returned. It is clear against generic siblings like buy_crypto_price, but it does not explicitly differentiate itself from the many buy_yields_chain_* / buy_yields_token_* siblings, relying on the name alone for routing.

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 resource named in the text; there is no statement of when to pick this over buy_yields_chain_pancake-adjacent chain tools or buy_yields_token_* tools, and no prerequisite guidance beyond payment. The pricing/auth sentences help an agent decide whether it can call at all, but not which tool to call.

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