Skip to main content
Glama

SouthPow crypto & market data

buy_cp_exchange-tokens

Paid. Live crypto prices, exchange tokens basket (BNB, OKB, CRO, GT): 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/exchange-tokens.

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_exchange-tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description is critical for behavioral transparency. It informs the agent about the payment required ('Paid'), the specific costs ($0.01 USDC on Base or Solana), and valuable failure modes (failed calls not charged).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely dense and information-packed, but every phrase serves a specific, essential function—defining the service, cost, and methodology. It is concise without being vague.

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 specialized, zero-parameter tool, the definition is maximally complete. It covers the 'what,' 'how,' and 'how much,' leaving no ambiguity for the agent before invocation.

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?

Since the input schema contains zero parameters, the description cannot add semantic meaning to parameters. It provides contextual data about the *output* (the basket of coins) which is noted, meeting the minimum viable score for a zero-parameter tool.

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?

The description is highly specific, identifying the exact resource (live crypto prices), the specific assets included (BNB, OKB, CRO, GT), and the methodology (USD median of Coinbase and Kraken). This specificity makes it highly distinct from generic price fetch tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool clearly defines its scope (the specific basket and calculation method) and constraints (paid, specific chains). While it doesn't explicitly state, 'Use this for this specific basket, not for single coin prices,' the detailed basket limitation serves as sufficient usage 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