Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_berachain

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

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

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

A4.1/5.0
Behavior5/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 so well: it discloses the paid cost ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that data comes from DefiLlama. These are exactly the traits (billing, auth, failure policy, provenance) an agent needs before spending money.

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 text is dense and front-loaded, leading with 'Paid' and then the data scope before cost and access terms. Every clause carries information, though the trailing raw URL is of marginal value to an agent that already has the tool wired up.

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 three-optional-parameter, no-output-schema tool, the description covers scope, return fields, price, auth, and failure billing, which is close to complete. Minor gaps remain around result shape/pagination beyond the limit parameter and whether the chain is fixed (it is, per the name).

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 the schema already documents sort, limit, and min_tvl_usd including defaults and ranges. The description only echoes the sort dimension ('by TVL or APY') and adds no syntax or constraint detail beyond that, so baseline 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?

The description states a specific verb and resource: live DeFi yields on Berachain, top pools ranked by TVL or APY. It also enumerates the returned metrics (base/reward APY, TVL, 7d APY change), which distinguishes it from the chain-level TVL sibling buy_tvl_berachain and from the other buy_yields_chain_* variants.

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 implied rather than stated: an agent can infer this is the tool for pool-level yield data on Berachain. There is no explicit 'use this instead of buy_tvl_berachain or buy_yields_protocol_* when...' routing, and no guidance on when a paid call is warranted versus a free sibling.

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