Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_flux-finance

Paid. Live DeFi yields for flux-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/flux-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_flux-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

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 burden and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), auth requirements (no account, no API key), and billing behavior on error (failed calls not charged), plus the upstream data source (DefiLlama). It omits rate limits and any notion of result ordering beyond the schema's sort parameter.

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 decisive fact ('Paid.') and then packs what you get, price, payment rails, and error billing into a few dense clauses with zero filler. The trailing endpoint URL is marginally redundant but serves as a concrete service identifier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns itself, and it does (cross-chain pools with APY, TVL, 7d APY change). Parameters are fully covered by the schema and the payment/authentication model is explicit, leaving nothing an agent needs in order to call this correctly.

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 the schema already explains sort, limit, and min_tvl_usd with defaults. The description adds no syntax or semantics for these filters, only the shape of the returned fields. Baseline 3 is appropriate.

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 resource and scope: live DeFi yield pools for the flux-finance protocol across chains, with the exact fields returned (APY, TVL, 7d APY change). Against a sibling set that splits yields by chain, token, and protocol, the protocol name in the tool name plus the description makes the target unambiguous.

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 resource ('yields for flux-finance'), and payment preconditions are spelled out, but there is no explicit when-to-use/when-not statement nor a named alternative (e.g. buy_yields_chain_* or buy_yields_token_* for cross-protocol views). The agent must infer selection from the naming convention.

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