Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_xrpl

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

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

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 behavioral burden and does it well: it discloses the tool is paid ($0.002 USDC on Base or Solana), requires no account or API key, does not charge failed calls, and sources data from DefiLlama. It omits rate limits, latency, and what a paid-but-empty result looks like, which keeps it from 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?

Telegraphic, front-loaded with 'Paid.' and packed with decision-relevant facts in four short sentences. The endpoint URL is the only element of marginal use to an agent that already has the tool, but it does no real harm.

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 output schema, the description compensates by enumerating the returned fields (base/reward APY, TVL, 7d APY change) and the cost model. Only the payment mechanics (how the $0.002 is actually settled) remain 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 three parameters (sort, limit, min_tvl_usd) are already documented in the schema. The description only echoes the sort dimension ('by TVL or APY') and says nothing about limit or min_tvl_usd behavior, 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?

States a specific verb and resource ('Live DeFi yields on XRPL: top pools by TVL or APY') plus the exact data returned. The chain scoping is baked into the tool name, so the description confirms rather than repeats, and an agent can distinguish it from buy_yields_protocol_* or buy_yields_stablecoins at a glance.

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: 'top pools by TVL or APY' tells the agent which sort values make sense, and the XRPL scope signals when to pick this over other chain variants. It never explicitly says when to prefer this over the protocol- or token-level yield tools, so the routing decision is left 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