Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_plume-mainnet

Paid. Live DeFi yields on Plume Mainnet: 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/plume-mainnet.

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_plume-mainnet"
  }
}

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.9/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 that the call is paid ($0.005 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. It omits rate limits and response shape, but the pricing and failure-charge behavior are exactly the non-obvious traits an agent needs before committing to a paid call.

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-loads "Paid." and then the data scope, pricing, and endpoint in a tight sequence with no filler. Slightly dense — the raw URL at the end is plumbing rather than agent-facing guidance — but nothing is wasted.

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 read tool with no annotations and no output schema, the description covers what the tool returns, where the data originates, and the payment model. The only meaningful gap is response format and pagination, which is a minor omission given the field list provided.

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 sort, limit, and min_tvl_usd are already documented. The description reinforces the sort semantics ("top pools by TVL or APY") but adds nothing about limit ranges or the default TVL floor, so it is a baseline pass rather than added meaning.

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?

States a specific verb and resource — live DeFi yields on Plume Mainnet, top pools by TVL or APY — plus the exact fields returned (base/reward APY, TVL, 7d APY change). The chain scope in the description and name cleanly separates it from the many buy_yields_chain_* 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?

Usage is implied by the chain scoping: an agent can infer this is the Plume variant versus buy_yields_chain_base or buy_yields_protocol_aave-v3. However, it never explicitly says when to choose chain-level yields over protocol-level yields, nor when not to call it; the routing has to be inferred from the name.

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