Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_apollo-diversified-credit-securitize-fund

Paid. Live DeFi yields for apollo-diversified-credit-securitize-fund: 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/apollo-diversified-credit-securitize-fund.

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_apollo-diversified-credit-securitize-fund"
  }
}

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 supplied, the description carries the full burden and does well: it discloses the paid cost ($0.005 USDC on Base or Solana), the payment rails, that no account or API key is needed, that failed calls are not charged, and that the data source is DefiLlama. It omits any hint about the response shape or pagination behavior, which keeps it from a 5.

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-loads the 'Paid.' warning, then purpose, then pricing and failure policy, then the endpoint URL. Every clause carries information; the trailing raw URL is slightly mechanical but genuinely useful for a paid endpoint.

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 zero-required-parameter read tool with no output schema and no annotations, the description covers purpose, returned metrics, cost, payment chain, auth-free access, failure policy, and data provenance. The only meaningful gap is return structure, which is partially implied by the listed metrics.

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% — sort, limit, and min_tvl_usd all have inline descriptions with defaults and ranges. The tool description adds nothing about these parameters, so the baseline 3 for schema-documented inputs applies.

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?

Names the specific resource (yields for the apollo-diversified-credit-securitize-fund protocol) and enumerates the returned fields: pools across chains, APY, TVL, 7d APY change. An agent knows exactly what data comes back. It does not explicitly distinguish itself from the many buy_yields_chain_* and buy_yields_token_* siblings, so it stops short of a 5.

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 implied by the scoping ('its pools across chains'), which tells an agent this is the protocol-level view rather than a chain or token query. However, it never states when to prefer buy_yields_chain_* / buy_yields_token_* / buy_yields_top, nor any preconditions beyond payment.

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