Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_tron

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

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

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 this is a paid call ($0.005 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It does not cover rate limits, per-call vs per-row billing, or pagination behavior, but the core cost/auth/failure profile is present.

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 the data payload in a compact, scannable sequence, with pricing and endpoint following. The trailing raw URL is marginal but plausibly useful for debugging; otherwise there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with no output schema, the description covers what is returned, the sort/filter semantics, payment cost and rails, authentication needs, and failure charging. Nothing an agent needs to decide or invoke correctly appears to be missing.

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% with defaults documented for sort, limit, and min_tvl_usd, so the schema does the heavy lifting. The description's 'top pools by TVL or APY' loosely maps to the sort parameter but adds no format or edge-case detail (e.g. string-typed numerics for limit/min_tvl_usd). 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?

States a concrete resource and scope: 'Live DeFi yields on Tron: top pools by TVL or APY' plus the returned fields (base/reward APY, TVL, 7d APY change) and data source (DefiLlama). That distinguishes it from the buy_tvl_tron sibling (chain-level TVL) and from buy_yields_protocol_* siblings, though it never names those alternatives explicitly.

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 payload description ('top pools by TVL or APY'), so an agent can infer it is a pool-listing lookup rather than a chain metrics or protocol drilldown. There is no explicit when-to-use/when-not or routing to sibling tools such as buy_tvl_tron or buy_yields_protocol_aave-v3, leaving selection partly to inference.

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