Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_savax

Paid. Where to earn yield on SAVAX: live pools holding SAVAX across protocols and chains, APY and TVL (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/token/savax.

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

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/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 handles the important parts: it is a paid call costing $0.01 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It omits data freshness/staleness and any rate-limit or settlement detail, keeping it short of 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.

Conciseness5/5

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

Front-loaded with the essential fact ('Paid'), then purpose, price, access constraints, and endpoint. Every sentence carries information an agent needs, with no repetition or 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 three-optional-parameter read tool with no output schema or annotations, the description covers resource scope, source, return fields (APY, TVL), payment, and failure policy. Missing are data freshness and any indication of response pagination or shape, but the core is 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?

Schema description coverage is 100%, so sort, limit, and min_tvl_usd are already fully documented with defaults. The description adds no parameter-specific meaning beyond that, which is acceptable at the baseline for fully covered schemas.

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: yield-earning pools holding sAVAX across protocols and chains, returning APY and TVL from DefiLlama. An agent can distinguish it from the many buy_coin_* price tools and buy_yields_chain_* chain-level tools because the token scope is explicit.

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?

The description implies when to use it (you want yield opportunities for sAVAX), but never names an alternative such as buy_yields_chain_avalanche or buy_coin_AVAX, nor states when not to use it. It does clarify the paid, keyless access model, which helps an agent decide whether calling is possible.

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