Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_ink

Paid. Live DeFi yields on Ink: top pools by TVL or APY with base/reward APY, TVL, 7d APY change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/chain/ink.

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

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.9/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 it discloses the most important behaviors: this is a paid call at $0.002 USDC on Base or Solana, no account or API key is needed, failed calls are not charged, and the data source is DefiLlama. It stops short of stating rate limits, caching/freshness, or error/payment-failure semantics beyond the no-charge guarantee.

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-loaded with 'Paid.' then purpose, then cost/access terms, then endpoint — no filler sentences. The raw URL is only marginally useful since transport is handled by the MCP layer, and the telegraphic stacking of terms is dense but readable.

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?

With no output schema, the description must describe return content, which it does by naming the metrics (base/reward APY, TVL, 7d change) and the data provider. Payment and access prerequisites are covered; only freshness/cadence and result-count semantics are left implicit, which the limit parameter largely handles.

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 schema already documents sort, limit, and min_tvl_usd. The description echoes the sort options and the returned metrics but adds no format, range, or default semantics beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (live DeFi yield pools on Ink), the ordering options (top by TVL or APY), and the exact fields returned (base/reward APY, TVL, 7d APY change). The chain scoping in 'on Ink' clearly separates it from the dozens of sibling buy_yields_chain_* and buy_yields_protocol_* tools.

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?

The description establishes the paid-usage context (cost, no account, failed calls not charged) but never says when to pick this over alternatives such as buy_tvl_ink for chain-level TVL or buy_yields_protocol_* for a single protocol. Usage is implied by the chain name rather than routed explicitly.

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