Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_sui

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

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

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 burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing rate limits, latency, or the response envelope/pagination.

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 the most decision-relevant fact ('Paid.') and then packs cost, payment rails, guarantees, and data scope into a few dense sentences with no filler. The telegraphic fragment style is efficient but slightly clipped.

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-parameter read endpoint with no annotations and no output schema, the description covers cost, access requirements, billing failure policy, data source, and the shape of returned fields. An agent has what it needs to decide and invoke, with only return formatting left implicit.

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 each parameter already carries its own default and description in the schema. The description echoes the sort semantics ('by TVL or APY') but says nothing about limit or min_tvl_usd behavior, so it adds little beyond the structured fields.

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 the resource precisely: live DeFi yield pools on the Sui chain, sourced from DefiLlama, with the fields returned (base/reward APY, TVL, 7d change). The chain scope differentiates it from the many buy_yields_protocol_* siblings, though it never names those alternatives or the closely related buy_tvl_sui.

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?

Implies usage via 'top pools by TVL or APY' and the payment terms, but gives no explicit when-to-use/when-not guidance and does not route the agent away from buy_tvl_sui or toward buy_yields_protocol_* when protocol-level data is wanted. Context is inferable but not 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