Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_yuzu-money

Paid. Live DeFi yields for yuzu-money: 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/yuzu-money.

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_yuzu-money"
  }
}

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 supplied, the description carries the full behavioral burden and does so well: it discloses the $0.01 USDC price, the two accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the upstream data source (DefiLlama). The only gap is that it does not describe result shape beyond the three named metrics or whether the call is read-only/side-effect free, which an agent could reasonably want spelled out.

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?

The text is dense and front-loaded, leading with cost and then what the tool returns, which is the right order for a paid tool. Every clause carries information (price, payment chains, failure policy, data source). The trailing raw URL is somewhat redundant with the tool name and endpoint naming, costing a small amount of space.

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 zero-required-parameter, read-only data lookup with no output schema, the description covers the essentials: what data comes back, where it comes from, what it costs, and how billing failures are handled. It would be fully complete if it hinted at the shape of the response (for example, a list of pool rows) or at behavior when no pools match.

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 types and defaults. The description adds no syntax, units, or interaction guidance for these filters (for example, how min_tvl_usd interacts with the default 100k threshold), 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?

The description names a specific resource (live DeFi yields for the yuzu-money protocol, across chains) and enumerates what is returned: APY, TVL, and 7d APY change. It is much clearer than a bare endpoint name. It stops short of a 5 because it never contrasts itself with the many sibling yield tools (buy_yields_chain_*, buy_yields_top, buy_yields_stablecoins), so the agent must infer the protocol-vs-chain-vs-global distinction from the tool name alone.

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-specific yield queries from 'its pools across chains'. There is no explicit when-to-use statement, no guidance on when to prefer a chain-level or top-yields sibling, and no mention of what happens with a narrow or empty result set. The payment and access conditions are covered, but selection guidance is not.

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