Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_flare

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

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

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.5/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 load and does well: it declares the tool is paid, names the exact price ($0.002 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the upstream data source (DefiLlama). It omits rate limits and response envelope/pagination behavior, which is the main remaining 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?

Very tight, front-loaded with the paid gate then the resource then the pricing and logistics. The raw endpoint URL tacked onto the end is the only element that does not obviously serve tool selection.

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?

No output schema exists, and the description compensates by enumerating the returned fields (base/reward APY, TVL, 7d APY change). Combined with pricing and access terms, an agent has enough to call it correctly; only ranking/ordering semantics and limits of the result set are 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 sort, limit, and min_tvl_usd are already documented with defaults. The description reinforces the sort dimension ("by TVL or APY") but adds no format, bounds, or interaction detail beyond the schema, 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?

"Live DeFi yields on Flare: top pools by TVL or APY" gives a specific verb+resource and pins the chain, which cleanly separates it from the many sibling chain variants and from the buy_yields_protocol_* family. It stops short of naming an alternative to steer away from, so it is clear but not explicitly differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Nothing states when to pick this over buy_yields_protocol_* (protocol-scoped) or buy_tvl_flare (aggregate TVL). The "Paid" prefix and pricing imply a cost trade-off but give no decision rule, so the agent must infer usage from the tool name alone.

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