Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_convex-finance

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

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_convex-finance"
  }
}

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

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it does well on cost, payment rails, account-free access and the no-charge-on-failure guarantee, plus 'Live' data freshness. However, it says nothing about rate limits, whether data is refreshed/cached, or what a successful response looks like, and it exposes no output schema.

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 the paid flag, then a compact content/data-source sentence, then pricing and access terms. Every sentence carries information, though the trailing bare URL is a bit awkward and could be folded into a single terms line.

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 paid data lookup with no output schema, the description covers cost, payment, failure behavior, data source and the fields surfaced, which is nearly everything needed to decide and call. The only real gap is the response envelope/pagination shape.

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%, and the description adds no meaning beyond the schema for sort, limit or min_tvl_usd. It does not even hint that results can be sorted by APY or TVL or filtered by a TVL floor, so the baseline of 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 (live DeFi yield pools for the convex-finance protocol across chains) and the fields returned (APY, TVL, 7d APY change, DefiLlama source). It is distinguishable from the coin/TVL/stablecoin siblings by name, though it never explicitly contrasts with buy_yields_chain_* or other buy_yields_protocol_* tools.

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 'yields for convex-finance' and the price/auth notes make it clear when calling is acceptable, but there is no explicit when-to-use vs. when-not guidance and no pointer to alternatives such as chain-level or token-level yield tools.

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