Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_jupsol

Paid. Where to earn yield on JUPSOL: live pools holding JUPSOL across protocols and chains, APY and TVL (DefiLlama data). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/token/jupsol.

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

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.8/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 burden and does well: it discloses that the tool is paid ($0.01 USDC on Base or Solana), requires no account or API key, that failed calls are not charged, and that data comes from DefiLlama. What it omits is return shape or pagination behavior, but the payment, auth, and billing-failure semantics are strong disclosures beyond what any structured field provides.

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 short, front-loaded with the payment flag and purpose, and every clause adds information: data scope, source, cost, auth model, billing policy, endpoint. No filler or redundancy.

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 and no annotations, the description covers what matters most: what the data is, where it comes from, what it costs, and that no auth is needed. The absence of any hint about result structure or result-count behavior is a minor remaining gap.

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 documented in the schema. The description adds no meaning about sorting behavior, row limits, or TVL filtering defaults. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific resource and scope: 'live pools holding JUPSOL across protocols and chains, APY and TVL (DefiLlama data)'. The token identity is both in the tool name and restated in prose, so it is clearly a token-level yield lookup. It does not explicitly distinguish itself from siblings like buy_yields_chain_solana or buy_yields_protocol_*, which is why it stops short of a 5.

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 token-specific scope: call this when you want yield opportunities for JUPSOL. However, there is no explicit guidance on when to prefer this over the chain-level (buy_yields_chain_solana) or protocol-level yield siblings, and no exclusions or prerequisites are stated. Adequate but leaves routing to inference.

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