Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_liquid-collective

Paid. Live DeFi yields for liquid-collective: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/liquid-collective.

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_protocol_liquid-collective"
  }
}

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 provided, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — important error/cost semantics an agent can't get elsewhere. It stops short of rate limits, response envelope, or pagination behavior, and the enumerated fields only partially cover the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the most decision-relevant fact ('Paid.'), then purpose, then cost, then access constraints, then endpoint — every fragment is information-dense with no hedging or filler. The telegraphic style suits a terse tool catalog.

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 3-optional-param read tool with no annotations and no output schema, the description covers cost, auth, failure billing, data source, and the metrics returned — enough for an agent to decide and call correctly. Only minor gaps remain around response structure and whether results are pool-level rows subject to limit/tvl filtering.

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 schema already documents sort, limit, and min_tvl_usd including defaults. The description adds no additional parameter meaning (no valid sort values, no unit or interaction notes), so the baseline of 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 and resource: live DeFi yield pools for the named protocol liquid-collective, with the concrete fields returned (APY, TVL, 7d APY change) and the data source (DefiLlama). The phrase 'its pools across chains' implicitly contrasts with the chain-scoped siblings (buy_yields_chain_*, buy_yields_token_*), but it never names an alternative 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 only implied: an agent can infer this is the tool for protocol-level yield data for liquid-collective rather than chain- or token-level yields. There is no explicit when/when-not guidance, no statement about what to do if the protocol has no pools, and no pointer to the sibling tools for other protocols or scopes.

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