Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_lbtc

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

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

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.5/5.0
Behavior3/5

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

With no annotations provided, the description bears the full behavioral load. It sets a clear commercial framing (pay per successful call, idempotent failure handling) and states that results are pool-level aggregates across chains. It omits staleness, error shapes, or what an empty result looks like.

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?

A single dense sentence covers capability, fields, and filters, followed by a short commercial note. It is tight and front-loaded, but packs unrelated payment details into the flow rather than keeping the capability statement clean.

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 parameterless-read yield lookup with no output schema, the description supplies enough: the token in scope, the metrics returned, the data source, and the cost model. Return shape (field names per row) is the only meaningful gap, and that is partially mitigated by the APY/TVL mention.

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 documented with defaults. The description adds nothing beyond the schema for any of the three parameters, which is acceptable given the complete coverage but leaves no extra semantic value.

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 a specific verb-resource pair: 'Pooled yield opportunities for LBTC sourced from DefiLlama,' plus the metrics returned (APY and TVL per pool) and the fact that it spans protocols and chains. The token-specific scope differentiates it implicitly from other siblings such as buy_yields_chain_* and buy_yields_protocol_*, though it never names an alternative explicitly.

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 LBTC scope: an agent wanting yield for LBTC specifically should use this instead of the chain or protocol siblings. However, the description never states when to prefer this over a protocol variant or a chain variant, nor what happens when no pools exist.

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