Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_pussy

Paid. Where to earn yield on PUSSY: live pools holding PUSSY across protocols and chains, APY and TVL (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/token/pussy.

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

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 that the tool is paid, the exact price and accepted payment chains, that no account or API key is needed, and that failed calls are not charged. What it omits is rate limits, behavior on empty results, and response shape, keeping it below 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.

Conciseness5/5

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

The purpose is front-loaded after the 'Paid' flag, and every remaining sentence carries a distinct fact: data source, price, payment chains, auth-free access, no charge on failure, and endpoint URL. There is no filler or repetition.

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 and no annotations, the description covers what is queried, where the data comes from, what fields come back (APY, TVL), and the commercial terms. Missing only edge-case behavior such as empty result sets or pagination limits.

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%, with sort, limit, and min_tvl_usd all documented including defaults, so the schema already does the work. The description adds no parameter-specific meaning such as valid sort values or how min_tvl_usd interacts with results, which is the baseline-3 outcome.

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 states a concrete purpose: live yield pools holding the PUSSY token across protocols and chains, with APY and TVL sourced from DefiLlama. That distinguishes it from the chain- and protocol-scoped yield siblings by resource scope. It stops short of naming a sibling to prefer, so it lands at 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?

Usage is implied by the token scoping ('pools holding PUSSY'), but there is no explicit when-to-use versus buy_yields_chain_* or buy_yields_protocol_* guidance. The commercial terms (paid, $0.002, no account) describe access rather than selection criteria, so an agent must infer routing on its own.

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