Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_mantle

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

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

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 burden and does substantial work: it discloses that the call is paid and the exact price, the accepted payment chains, that no account or API key is required, that failed calls are not charged, and the upstream data source (DefiLlama). It stops short of stating rate limits, cache freshness, or an error/response contract, which keeps it below a 5.

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.' followed by the data scope, then commercial terms, then the endpoint URL – each clause carries distinct information an agent needs. The URL tacked on the end is the only element that reads as appended rather than woven in.

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, and the description compensates by naming the returned fields (base/reward APY, TVL, 7d APY change). For a three-optional-parameter read tool, payment and access requirements are also covered; only freshness/latency and result-count 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 including defaults. The description echoes the sort dimension ('by TVL or APY') and the rank basis but adds no syntax, units, or edge-case guidance beyond the schema; baseline 3 is appropriate.

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 pairs a specific verb and resource ('Live DeFi yields on Mantle') with the exact payload ('top pools by TVL or APY with base/reward APY, TVL, 7d APY change'), which is enough to separate it from the buy_yields_protocol_* and buy_tvl_* siblings. It never explicitly contrasts itself with the other chain-yield tools, but the chain scope is unambiguous.

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 by 'Live DeFi yields on Mantle' plus the sort choices, and the payment facts ($0.002 USDC on Base or Solana, no account/key) tell an agent what it must have in place before calling. However, there is no 'when to use this instead of X' guidance – nothing points an agent to buy_tvl_mantle for chain-level TVL or to the protocol-level yield tools for a single protocol.

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