Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_curve-llamalend

Paid. Live DeFi yields for curve-llamalend: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/curve-llamalend.

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_curve-llamalend"
  }
}

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
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 that the call is paid, the exact price ($0.005 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It also names the underlying data source and returned fields. It does not say how fresh or cached the data is.

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 entry is front-loaded with the 'Paid' flag, then purpose, then return fields, then pricing and access terms. Every clause carries information; the only slightly awkward element is the raw URL appended at the end rather than presented as an endpoint field.

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 read-only, three-optional-parameter paid endpoint, the description covers cost, payment mechanism, auth requirements, billing on failure, and the returned metrics, which is what an agent needs to decide whether to spend money. The lack of an output schema is partly offset by the field list, but response shape and data freshness remain unstated.

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%, with sort, limit, and min_tvl_usd each documented including defaults and ranges, so the baseline is 3. The description adds nothing about parameter behavior (e.g., how sorting interacts with the default TVL floor or row limits), so it earns no credit above baseline.

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?

States a specific resource (curve-llamalend pools across chains) and enumerates the returned fields (APY, TVL, 7d APY change, DefiLlama source). The protocol name in the tool name and the description line up, so an agent can tell it apart from the many other buy_yields_protocol_* siblings without opening a schema, though the description never explicitly contrasts itself with the chain-level or token-level 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. Given dozens of sibling yield tools (per-chain, per-token, per-protocol), the description gives no routing rule such as 'for all pools on a chain use buy_yields_chain_*' or 'for a different protocol use the matching buy_yields_protocol_* tool'.

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