Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_kamino-lend

Paid. Live DeFi yields for kamino-lend: 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-lend.

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

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 does well: it discloses paid pricing ($0.002 USDC on Base or Solana), no account or API key, that failed calls are not charged, and the upstream data source. It stops short of describing rate limits, data freshness, or the response shape, so it is strong but not exhaustive for a paid tool.

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 the salient 'Paid.' signal, then the resource and fields, then pricing and access terms — no wasted sentences. The telegraphic fragment style ('$0.002 USDC on Base or Solana. No account, no API key.') is dense rather than padded, though it reads as marketing copy as much as specification.

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 3-optional-parameter read tool with no output schema, the description conveys what data comes back (pools, APY, TVL, 7d change), cost, and payment rails. It could still say more about response shape or row-count behavior since no output schema exists, but the essentials for a correct call are present.

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/tvl-vs-apy, limit range, and min_tvl_usd default are already documented in the schema. The description adds no syntax or behavioral detail about these filters (for example, how min_tvl_usd interacts with the returned rows), so the baseline 3 applies.

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 verb+resource: live DeFi yields for the kamino-lend protocol, with named fields (APY, TVL, 7d APY change) and a named data source (DefiLlama). The protocol is scoped narrowly enough that an agent can distinguish it from the many buy_yields_protocol_* siblings such as kamino-liquidity and from the buy_yields_chain_* family.

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 protocol name, and payment/no-auth context is given, but there is no explicit when-to-use or when-not guidance — nothing says to use buy_yields_chain_solana for chain-wide yields or buy_yields_protocol_kamino-liquidity for the other Kamino product. An agent must infer routing from the name alone.

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