Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_ondo-yield-assets

Paid. Live DeFi yields for ondo-yield-assets: 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/ondo-yield-assets.

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_ondo-yield-assets"
  }
}

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 present, the description carries the full burden and does it well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and that the data originates from DefiLlama. What remains undisclosed is rate limiting and how the returned rows are shaped or paginated.

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 paid status is front-loaded as a single word, followed by data scope, cost/access terms and endpoint, so an agent learns the commitment before the content. The closing URL and the dense price sentence are slightly list-like but every element is actionable.

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?

With three optional parameters, no output schema and no annotations, the description compensates by naming the returned metrics and the upstream data source. A caller still has to infer response shape and pagination behavior, but nothing needed to decide whether to call it is 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 inline. The description mentions the returned fields (APY, TVL, 7d change) but adds no filtering or sorting semantics beyond what the schema supplies, making the baseline 3 appropriate.

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 concrete verb and resource: live DeFi yields for the ondo-yield-assets protocol, returned per pool with APY, TVL and 7d APY change. The phrase 'its pools across chains' scopes it as protocol-wide, which implicitly separates it from the chain-scoped and token-scoped yield siblings, though no sibling is named 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 only implied by the protocol name in the tool name and the 'pools across chains' phrasing; there is no explicit statement of when to pick this over buy_yields_protocol_* neighbors or buy_yields_chain_base. Payment and access conditions are covered, but task-selection guidance is not.

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