Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_gtusdcp

Paid. Where to earn yield on GTUSDCP: live pools holding GTUSDCP 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/gtusdcp.

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits, response envelope/pagination shape, and what happens on partial data, which keeps it below 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, with a compact telegraphic style and no filler. The endpoint URL is justified for a metered x402-style API. Slightly clipped phrasing ('Paid.', 'URL ...') costs a point versus fully formed prose.

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?

For a read-only data-lookup tool with no output schema, the description covers what data comes back (pools, protocols, chains, APY, TVL), its source, the cost and settlement rails, and the failure-billing policy. Nothing essential to calling it correctly is missing.

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% and each of the three parameters (sort, limit, min_tvl_usd) already has its defaults and ranges documented in the schema. The description adds no parameter-level meaning such as how sorting interacts with min_tvl filtering, so the baseline 3 applies.

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?

States precisely what is returned: live pools holding GTUSDCP across protocols and chains, with APY and TVL, sourced from DefiLlama. The token-specific scope (GTUSDCP) cleanly distinguishes it from the dozens of sibling buy_yields_token_* and buy_yields_chain_*/protocol_* tools without needing to open any schema.

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 scope: call this when you want yield opportunities for GTUSDCP specifically. However, it never states when to prefer a sibling instead (e.g. buy_yields_stablecoins, buy_yields_top, or the chain/protocol variants) or notes any prerequisites beyond payment. The payment instructions are behavioral context, not selection guidance.

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