Skip to main content
Glama

SouthPow crypto & market data

buy_yields_token_senrlusdv2

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

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

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.9/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 behavioral burden and does a fair job: it discloses the paid model ($0.005 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It does not cover rate limits, pagination, or response shape, which keeps it short of 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?

Dense and front-loaded: 'Paid.' then purpose, then data source, price, auth, and URL. Nearly every clause earns its place, though the payment/auth clauses could be compressed into one sentence.

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-param read-only lookup with no output schema and no annotations, the description supplies the key facts an agent needs: what is returned (pools, protocol, chain, APY, TVL), the data source, and the payment/auth mechanics. Only result pagination and exact response shape remain unaddressed.

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 (tvl|apy), limit (1-100), and min_tvl_usd are already documented. The description adds no syntax, default, or interaction detail beyond the schema, 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 a specific verb and resource: 'Where to earn yield on SENRLUSDV2: live pools holding SENRLUSDV2 across protocols and chains, APY and TVL (DefiLlama data).' An agent can tell this apart from the many sibling families (buy_yields_protocol_*, buy_yields_chain_*, buy_yields_token_<other token>) because the token scope and returned fields are explicit.

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 description ('where to earn yield on SENRLUSDV2'), but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use buy_yields_protocol_* to pivot by protocol, or buy_yields_token_sxsrlusd for a related token). The rest of the text covers pricing, not routing 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