Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_kinetiq-khype

Paid. Live DeFi yields for kinetiq-khype: 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/kinetiq-khype.

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_kinetiq-khype"
  }
}

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.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Since no annotations are provided, the description must carry the behavioral burden. It excels here by disclosing costs, accepted chains, authentication needs, and failure policies ('Failed calls not charged'), making it very transparent about execution behavior.

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?

The description is highly efficient, front-loading the core service and following it with necessary operational details. Every sentence contributes significantly to clarity and user adoption.

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?

Given that this is a highly specific, protocol-named tool within a family of similar tools, the description is exceptionally complete. It covers what, where, how much, and how to use the service.

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 perfect (100%). The description adds contextual value by specifying the data source ('DefiLlama data') and what metrics are provided (APY, TVL, 7d APY change), preventing the score from being lower than the baseline 3.

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?

The description clearly identifies the tool's function as providing 'Live DeFi yields' specifically for 'kinetiq-khype'. The high level of specificity regarding the protocol name makes it unambiguous.

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

Usage Guidelines5/5

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

It provides strong operational guidance by detailing the required currency and network ('$0.005 USDC on Base or Solana'). It also clarifies the lack of prerequisite setup by stating 'No account, no API key,' which is critical usage information.

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