Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_lombard-lbtc

Paid. Live DeFi yields for lombard-lbtc: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/lombard-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_protocol_lombard-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

A4/5.0
Behavior4/5

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

With no annotations, the description supplies substantial operational detail: live DefiLlama sourcing, a $0.01 USDC charge, payment on Base or Solana, no account or API key, and no charge for failed calls. It does not explicitly label the operation read-only, and "live" leaves caching or freshness behavior unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads both paid status and protocol-specific purpose. Cost, payment networks, authentication requirements, failure billing, and the endpoint each add operational value with little redundancy.

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 simple three-parameter data lookup, the scope, source, principal returned metrics, and commercial terms are enough to invoke it confidently. Because there is no output schema, the exact response envelope and available chain or pool identifiers remain unspecified, and sibling-selection guidance is absent.

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?

All three optional parameters are already documented in the schema, including defaults and ranges, so the high-coverage baseline applies. The description adds no guidance on choosing TVL versus APY sorting or on combining the minimum-TVL filter with the row limit.

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 identifies a live, protocol-specific yield-pool lookup for lombard-lbtc and lists APY, TVL, and 7d APY change, clarifying that "buy" refers to purchasing data rather than an asset. It does not explicitly contrast this protocol view with the similarly named token, chain, or top-yield siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrases "for lombard-lbtc" and "its pools across chains" establish a clear use case: retrieving cross-chain pool yields for this one protocol. There is no when-not guidance or routing to buy_yields_token_lbtc, chain-specific yield tools, or buy_yields_top.

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