Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_ipor-fusion

Paid. Live DeFi yields for ipor-fusion: its pools across chains with 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/protocol/ipor-fusion.

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_ipor-fusion"
  }
}

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 supplied, the description carries the full behavioral burden and does well: it discloses the paid model, the exact price and accepted payment chains, the absence of auth requirements, the no-charge-on-failure policy, and the upstream data source (DefiLlama). It omits return shape, pagination and rate limits, which keeps 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.

Conciseness4/5

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

Front-loads the 'Paid.' flag, then purpose, then pricing and access terms in tight fragments with no filler. The endpoint URL is the only element of questionable value, though it does support a direct HTTP fallback.

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 tool with no output schema, the definition covers purpose, data source, cost and access. Because there is no output schema, the brief enumeration of returned metrics is genuinely useful; only the response/pagination shape is left unstated.

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 in the schema with defaults and ranges. The description adds no syntax or semantics for these parameters, so the baseline 3 applies; its field list (APY, TVL, 7d APY change) describes outputs rather than inputs.

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 a specific resource and scope: live DeFi yields for the ipor-fusion protocol, with pools across chains and the fields APY, TVL and 7d APY change. That scoping implicitly separates it from the chain-level and token-level yield siblings, though it never names an alternative explicitly.

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?

It gives useful commercial context (paid, $0.005 USDC on Base or Solana, no account or API key, failed calls not charged), which helps an agent decide whether it can call it at all. However, there is no explicit guidance on when to pick this over buy_yields_chain_* or buy_yields_token_* for overlapping queries.

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