Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_slisbnb

Paid. Where to earn yield on SLISBNB: live pools holding SLISBNB across protocols and chains, APY and TVL (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/token/slisbnb.

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

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 cost ($0.002 USDC), accepted payment chains (Base or Solana), no auth requirement, and that failed calls are not charged — unusually complete for a paid tool. It stops short of rate limits, caching freshness beyond 'live', or result ordering behavior.

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-loads the purpose, then pricing, then access terms in a tight sequence with no filler. The trailing bare URL is slightly abrupt but serves a real function for payment/routing.

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?

No output schema exists, yet the description names what comes back (pools across protocols and chains with APY and TVL), which is the key missing piece an agent needs to judge usefulness. Remaining gaps — exact response fields and empty-result behavior for an obscure token — are minor.

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 in the input schema. The description adds no further meaning about defaults or how min_tvl_usd interacts with the sort mode, 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 resource (yield pools holding SLISBNB), a specific scope (across protocols and chains), and the data returned (APY and TVL from DefiLlama). Against siblings like buy_yields_chain_base or buy_yields_protocol_aave-v3, an agent can immediately tell this is the token-centric yield lookup for SLISBNB.

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 covers access conditions (paid, no account, no API key, failed calls free) but never says when to prefer this over buy_yields_chain_* or buy_yields_protocol_* siblings, nor when a token with no live pools would return empty. Usage is implied by the token name rather than explained.

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