Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_aerodrome-v1

Paid. Live DeFi yields for aerodrome-v1: 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/aerodrome-v1.

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_aerodrome-v1"
  }
}

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

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the prose carries the behavioral burden and does it well: it discloses that calls are paid, the exact $0.01 USDC price, Base or Solana payment options, no account or API key requirement, and no charge for failed calls. "Live" data and DefiLlama attribution add freshness and provenance context, while the retrieval framing implies no state-changing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the paid nature and core data offering before practical invocation details. Each short statement contributes distinct information—scope, metrics, source, cost, authentication, failure billing, or endpoint—with no filler.

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 lookup with three optional, fully documented parameters, the combined definition supplies enough to select and invoke it: protocol scope, cross-chain coverage, key metrics, source, endpoint, and payment behavior. Because there is no output schema, the lack of a fuller response-row description and the absence of explicit sibling routing keep it short of fully complete.

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?

All three optional parameters are already documented in the schema, including allowed sort values, ranges, and defaults, so the baseline is 3. The description does not add further syntax, interactions, or examples for sort, limit, or min_tvl_usd.

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 identifies a concrete resource and scope: live Aerodrome v1 pool yields across chains, with APY, TVL, and 7-day APY change. Naming aerodrome-v1 and the cross-chain protocol scope distinguishes it from aerodrome-slipstream and the chain-, token-, and top-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 Guidelines4/5

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

It gives a clear use case: obtaining Aerodrome v1 pool yield and TVL data across chains from DefiLlama. It does not explicitly say when to prefer buy_yields_chain_*, buy_yields_token_*, buy_yields_top, or the Aerodrome Slipstream sibling, so there are no explicit exclusions or 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