Skip to main content
Glama

SouthPow crypto & market data

buy_yields_protocol_pareto-credit

Paid. Live DeFi yields for pareto-credit: its pools across chains with APY, TVL, 7d APY change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/yields/protocol/pareto-credit.

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_protocol_pareto-credit"
  }
}

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.002 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. That covers cost, auth model, and error-billing semantics. It omits rate limits, pagination/response-size behavior, and data freshness/latency, 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?

It is front-loaded with the most decision-critical fact ("Paid.") and then packs what it returns, the price, the payment rails, the auth requirement, the failure policy and the endpoint into a few dense clauses. No sentence is filler, though the telegraphic style and trailing raw URL read slightly like metadata rather than prose.

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 tool with no annotations and no output schema, the description compensates well by naming the returned fields (APY, TVL, 7d APY change) and the data source, plus payment and auth details. Remaining gaps — pagination, rate limits, error shapes — are modest for a read-only paid data endpoint.

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% — sort, limit and min_tvl_usd all have inline descriptions including defaults and ranges — so the schema already does the semantic work. The description adds no parameter-level meaning beyond that, which is the expected 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?

The description names a specific resource and scope: pool-level yields for the pareto-credit protocol, across chains, with APY, TVL and 7d APY change sourced from DefiLlama. The protocol name in the tool name plus the description makes it distinguishable from the many other buy_yields_protocol_* siblings, though the description never explicitly contrasts itself with chain-, token-, or top-level yield 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 infers it should call this when it wants yield data for pareto-credit specifically. There is no explicit when-to-use or when-not-to-use guidance, and no alternative (e.g. buy_yields_chain_* for cross-protocol chain views, buy_yields_token_* for token-centric views) is named to route the agent.

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