Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_buidl

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

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

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 declares the tool is paid, the exact price ($0.005 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the upstream data source. It stops short of describing response shape or whether results are paginated beyond the limit parameter.

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 'Paid.' followed by one sentence of purpose and one of commercial terms; there is no filler. The raw URL at the end is slightly awkward but functions as a concrete endpoint reference.

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 three-optional-parameter paid query with no output schema and no annotations, the description covers cost, payment rails, authentication requirements, failure billing, and data provenance. Only the returned fields and row-level shape remain unspecified, which is a modest gap.

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 and ranges. The description only alludes to APY and TVL being present, which does not add semantics beyond the schema, so the baseline of 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?

The description names a specific resource and scope: live yield pools holding BUIDL across protocols and chains, returning APY and TVL from DefiLlama. That distinguishes it from the many buy_yields_token_* siblings (different token) and from buy_stable_buidl (stablecoin metadata rather than yield venues).

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?

The phrase 'Where to earn yield on BUIDL' implies the use case but never states when to prefer this over buy_yields_protocol_blackrock-buidl or the chain-level yield tools. No exclusions or alternative routing are given, so the agent must infer selection from the token 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