Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_blackrock-buidl

Paid. Live DeFi yields for blackrock-buidl: 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/blackrock-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_protocol_blackrock-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.7/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 so well: it discloses a paid call ($0.005 USDC on Base or Solana), no account or API key required, no charge for failed calls, and the underlying data source (DefiLlama). Remaining gaps are rate limits and error 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-loaded with 'Paid' and the core purpose, then compact clauses covering data, price, access, and endpoint. Telegraphic fragments are efficient, though the bare URL is somewhat raw and the sentence fragments border on staccato.

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, so the description correctly summarizes the returned fields (APY, TVL, 7d change), and it fully covers cost, payment methods, and access requirements. Only error/shape details and pagination limits beyond the schema's are missing.

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 in the schema; the description adds nothing about them. Baseline 3 applies when the schema does the parameter work.

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 verb and resource: live DeFi yield pools for the blackrock-buidl protocol, with the fields returned (APY, TVL, 7d APY change). It is distinguishable from chain- and token-scoped yield siblings by naming the protocol scope, though it never explicitly contrasts with buy_yields_token_buidl or buy_stable_buidl.

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?

Use is only implied by the protocol scope and the price signal; there is no explicit 'use this when' statement or routing to sibling tools such as buy_yields_token_buidl for a token-level view. The payment and no-account notes give context for deciding to call, but not when to prefer this over alternatives.

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