Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_kamino-liquidity

Paid. Live DeFi yields for kamino-liquidity: its pools across chains with 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/protocol/kamino-liquidity.

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_kamino-liquidity"
  }
}

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 at all, the description carries the full behavioral burden and does well: it discloses the paid model, exact price, accepted payment chains, no-account/no-API-key access, and that failed calls are not charged. Gaps remain around return shape, pagination, and any rate limits, but the commercial and auth behavior an agent most needs before spending money is explicit.

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 opening 'Paid.' front-loads the most decision-relevant fact, and the data/price/access details follow in a tight sentence chain. The raw URL is somewhat extraneous for an agent that already has the endpoint, but nothing bloats the text.

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?

All three parameters are optional with full schema coverage and there is no output schema, so the description's enumeration of returned metrics (APY, TVL, 7d change) usefully compensates for the missing return definition. Only pagination/response-shape detail is absent, which is minor for a simple list endpoint.

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 fully documented with defaults. The description adds nothing about parameter behavior or interactions (e.g., how min_tvl_usd filtering interacts with sort), 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 the exact resource (Kamino Liquidity pools across chains) and the fields returned (APY, TVL, 7d APY change, sourced from DefiLlama). The protocol slug in the tool name disambiguates it from the many sibling protocol-yield tools. It never uses an explicit verb like 'fetch/return', relying on the 'buy_yields' prefix to convey the action.

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?

It states the cost ($0.002 USDC on Base or Solana) and that failed calls are free, which lets an agent weigh whether to call it. However, it gives no when-to-use framing and names no alternative — for example, whether a caller wanting Kamino lending markets should use the sibling kamino-lend tool instead is left to inference.

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