Skip to main content
Glama

SouthPow crypto & market data

buy_yields_chain_near

Paid. Live DeFi yields on Near: 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/near.

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

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 present, the description still carries the important behavioral facts: it is paid, costs $0.01 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It omits rate limits and does not flag that these are live/volatile readings or how many rows/pagination behaves beyond the limit parameter.

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?

Front-loaded with the key gating fact ('Paid.'), then the data content, then cost/auth terms in short declarative sentences. No filler; even the URL is a single useful token.

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 simple read-only endpoint with three optional parameters and no output schema, the description covers cost, auth, source and the returned fields, which compensates for the missing output schema. Only minor gaps remain (rate limits, response size/pagination).

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% with defaults documented for all three parameters, so the baseline is 3. The description reinforces the sort dimension ('TVL or APY') but adds nothing about limit or min_tvl_usd beyond what the schema already states.

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?

Names the specific resource (live DeFi yields on Near), the selection modes ('top pools by TVL or APY'), the returned fields (base/reward APY, TVL, 7d APY change) and the upstream source (DefiLlama). The chain qualifier cleanly separates it from the many sibling buy_yields_chain_* and buy_yields_protocol_* tools.

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 only implied: an agent can infer this is the Near-chain yield lookup, but the description never states when to prefer it over buy_tvl_near, buy_yields_token_*, or the protocol-level yield tools. No exclusions or prerequisites are given beyond the payment note.

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