Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_pt

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

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

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, the description carries the full load and does meaningful work: paid access at $0.002 USDC on Base or Solana, no account or API key required, and failed calls are not charged. That is exactly the kind of operational context an agent needs before spending money. It stops short of stating rate limits, response shape, or what an empty result means.

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-loaded with 'Paid.' so cost is known before anything else, then purpose, then payment mechanics, then endpoint. Telegram-style fragments but every sentence carries information; nothing is redundant.

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 three-optional-parameter read tool with no annotations or output schema, the description covers what the data is, where it comes from, what it costs, and how to pay. The only real gap is that the return structure is only hinted at via 'APY and TVL'.

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%, so sort, limit, and min_tvl_usd are already fully documented in the schema, including defaults and ranges. The description adds no parameter guidance beyond that, which is acceptable given the coverage but earns only the baseline.

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 verb-of-sorts: live pools holding PT, with APY and TVL across protocols and chains, sourced from DefiLlama. Clear enough to distinguish from chain- and protocol-scoped yield siblings, though it never names an alternative.

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?

Implied usage — query this when looking for yield opportunities on the PT token — but there is no explicit when-to-use vs. when-not guidance, and no routing to siblings like buy_yields_protocol_* or buy_yields_chain_* even though those are the obvious alternates.

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