Skip to main content
Glama

SouthPow crypto & market data

buy_cp_defi

Paid. Live crypto prices, defi basket (UNI, AAVE, MKR, LDO, CRV, COMP, SNX, SUSHI, 1INCH, PENDLE): USD median of Coinbase and Kraken, each source shown. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/defi.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 the price ($0.01 USDC), the two accepted payment chains (Base or Solana), the absence of account/API key requirements, and the failure policy ('Failed calls not charged'). It also explains the price derivation (median of Coinbase and Kraken, both sources shown). Rate limits, latency, and response shape are not covered.

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.' and then the payload, cost, payment rails, and failure policy. Telegraphic style is efficient for an agent, though the parenthetical ticker block is long and could be trimmed without losing selection signal.

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 zero-parameter tool with no output schema and no annotations, the definition supplies everything needed to decide to call it: what data, what it costs, how to pay, that no credentials are needed, and that failures are free. The only shortfall is that the exact response structure beyond 'each source shown' is undefined.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The ticker list is documentation of scope rather than of arguments, which is the right use of the space.

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 verb+resource ('Live crypto prices, defi basket') and enumerates the ten basket constituents, which in practice separates it from the single-asset buy_coin_UNI / buy_coin_AAVE siblings and the other buy_cp_* basket tools. It stops short of naming an alternative outright, so the differentiation is inferred from the ticker list rather than stated.

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 basket contents: an agent can infer this is the multi-token DeFi call rather than a single-coin call. There is no explicit 'use this when...' or 'prefer X for a single token' statement, and no guidance on precedence versus buy_cp_ethereum-ecosystem or buy_cp_majors, which overlap in holdings.

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