Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_robinhood-chain

Paid. Live DeFi yields on Robinhood Chain: 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/robinhood-chain.

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_robinhood-chain"
  }
}

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 well: it discloses that the call is paid ($0.002 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It omits rate limits, timeout/latency expectations and result-set size behavior, so it falls short of 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?

It is front-loaded with the purpose and then the commercial terms, with no filler sentences. The trailing raw endpoint URL ('https://southpow.media/v1/...') adds little for an agent choosing a tool and is the one expendable element.

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 simple three-optional-parameter read tool with no output schema, the description covers pricing, auth, data source and the returned fields, which is close to complete. It lacks only pagination/result-size expectations and explicit sibling routing.

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 with defaults. The description only echoes the sort choice ('by TVL or APY') and adds no format or filtering nuance beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Live DeFi yields on Robinhood Chain: top pools') plus the exact fields returned (base/reward APY, TVL, 7d APY change) and the data source (DefiLlama). The chain name in the text separates it from the many buy_yields_chain_* siblings, but it never explicitly says 'not other chains/protocols', leaving differentiation implicit.

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: you would call this to see top pools on Robinhood Chain ranked by TVL or APY. There is no explicit when-to-use/when-not guidance relative to alternatives such as buy_tvl_robinhood-chain (TVL-only) or buy_yields_protocol_* (protocol-level yields), which an agent would likely confuse.

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