Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_unichain

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

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

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

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Since no annotations were provided, the description carries the full weight and does an exceptional job. It discloses critical operational traits such as being a paid tool, the data source (DefiLlama), the cost ($0.005 USDC on Base or Solana), and key operational benefits like 'No account, no API key' and 'Failed calls not charged.'

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 description is highly information-dense, managing to cover cost, source, topic, and operational features in a single, front-loaded paragraph. Every sentence is packed with valuable, actionable information for the AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool definition is highly complete for a data-fetching operation. It provides the data source, the operational costs, the payment methods, and the specific chain coverage. This level of operational detail is extremely useful for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema covers the parameters, the description adds semantic context to them. It explains that the tool queries 'top pools' and specifies that the user can sort by 'TVL or APY' metrics. This helps the agent understand the intent behind the input values in the context of DeFi pools.

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 clearly defines the tool's function: listing live DeFi yields for Unichain pools. Although the name implies a purchase, the description correctly clarifies it provides yield data and metrics like TVL and APY. It distinguishes itself by explicitly naming the chain, Unichain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool is strictly scoped to Unichain and is presented as the definitive source for this specific data. The extensive list of sibling tools (e.g., other chain yield tools) allows an agent to use context to decide when this specific tool is necessary. It lacks an explicit 'when not to use' clause, but the specificity compensates.

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