Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_gnosis

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

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

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 zero annotations the description carries the full burden and does real work: it discloses that the call is paid ($0.005 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and the upstream data source (DefiLlama). Missing is any hint about rate limits, caching/refresh cadence of 'live' data, or response shape detail beyond field names.

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 the key qualifier 'Paid' and then packs scope, output fields, price, payment rails, and auth requirements into a compact block. The trailing bare URL is slightly boilerplate but functional; nothing is padded.

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, so the description usefully enumerates the returned fields (base/reward APY, TVL, 7d APY change), which is exactly what an agent needs to decide whether to call it. Payment and auth are also covered. It lacks any note on result ordering guarantees or empty-result behavior, but it is broadly complete for a 3-optional-param read tool.

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%, so the three parameters (sort, limit, min_tvl_usd) are already fully documented including defaults. The description's 'top pools by TVL or APY' corroborates the sort parameter but adds no format, range, or interaction detail 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?

States a specific verb+resource+scope: 'Live DeFi yields on Gnosis' with 'top pools by TVL or APY'. An agent can distinguish it from the dozens of sibling buy_yields_chain_* tools purely by the chain named in the description. It does not explicitly contrast with adjacent siblings like buy_tvl_gnosis or buy_yields_protocol_*, so 4 rather than 5.

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?

Implied usage is clear (fetch ranked yield pools for one chain), and the 'top pools by TVL or APY' phrase hints at the sort choice. However, there is no explicit when-to-use vs. when-not guidance, no mention of the buy_tvl_gnosis sibling for chain-level TVL, and no note on when a protocol-scoped yields tool would be preferable.

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