Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_aerodrome-slipstream

Paid. Live DeFi yields for aerodrome-slipstream: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/aerodrome-slipstream.

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

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 behavioral burden and does well: it discloses the paid model ($0.002 USDC on Base or Solana), that no account or API key is needed, that failed calls are not charged, and the DefiLlama data source. Remaining gaps are rate limits and whether the price is per call regardless of row count.

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 'Paid.' before the purpose, then packs payload, price, auth, and billing behavior into three dense sentences with no filler. The trailing bare URL is slightly awkward but is a legitimate 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 3-optional-param paid data endpoint with no output schema and no annotations, the description covers cost, auth, failure billing, data source, and returned fields — enough for an agent to decide and call correctly. Only the default-TVL filtering implication and per-call pricing granularity are left unstated.

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 already document their own meaning and defaults. The description adds no parameter guidance at all — it doesn't note that min_tvl_usd defaults to 100000 and will silently truncate small pools — so baseline 3 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?

States a specific resource and payload: 'Live DeFi yields for aerodrome-slipstream: its pools across chains with APY, TVL, 7d APY change', so an agent knows exactly what data comes back. It does not explicitly contrast itself with chain-scoped siblings like buy_yields_chain_base or with buy_yields_protocol_aerodrome-v1, leaving routing to inference from the name.

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?

Invocation logistics are covered (cost, payment chains, no account/API key) but there is no when-to-use guidance relative to alternatives — nothing says to pick chain-level tools when a chain filter is wanted, or that this is the pool-level view of one protocol. Usage is implied by the protocol name rather than stated.

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