Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_mezo

Paid. Live DeFi yields on Mezo: top pools by TVL or APY with base/reward 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/chain/mezo.

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

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.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does more than most: it discloses that this is a paid call ($0.005 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It doesn't state refresh cadence beyond 'Live' or any rate limits, and it never explicitly says the call is read-only, which is the main residual gap.

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?

Dense but front-loaded: the paid status and the core purpose come first, then the data fields, then pricing/auth/failure terms. Each clause carries distinct information; only the raw endpoint URL is arguably expendable, though it does serve the transparency goal.

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 three-parameter, no-required-input read tool with no output schema, the description reasonably enumerates the returned fields (base APY, reward APY, TVL, 7d change) and covers commercial terms. What remains thin is guidance on result volume/pagination behavior beyond the limit parameter.

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 coverage is 100%, so all three parameters (sort, limit, min_tvl_usd) are already documented in the schema. The description echoes the TVL/APY sort choice but adds nothing about limit bounds or the min_tvl_usd threshold, so the baseline 3 applies.

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?

States a specific verb and resource ('Live DeFi yields on Mezo: top pools by TVL or APY') and pins the scope to one chain, which is exactly what separates it from the numerous buy_yields_chain_* siblings. The field list (base/reward APY, TVL, 7d APY change) further confirms what data comes back.

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 chain scope and the DefiLlama data source, but there is no explicit 'use this when… / use X instead when…' routing, nor a statement about when TVL-sorting vs APY-sorting is appropriate. An agent can infer the right context from the name, but the description doesn't do the routing work.

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