Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CACAO

Paid. Maya Protocol (CACAO) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CACAO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that the call is paid, the exact price and accepted payment chains (USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and the underlying URL. Not covered are rate limits or response shape beyond the field list, 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?

Six short fragments, front-loaded with the payment status and then the data scope. Nothing is redundant, though the mix of pricing, auth, and endpoint facts in one flat run of sentences makes it slightly harder to scan than grouped clauses would be.

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, the description supplies the essentials: what data comes back (price, 24h change, market-cap rank), what it costs, how to pay, and that there is no auth. It stops short of describing the response envelope or freshness guarantees, which would fully close the gap.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing inputs and instead spends its words on scope and cost.

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 concrete resource and payload: 'Maya Protocol (CACAO) price: live USD price, 24h change and market-cap rank.' That is a specific verb-less but unambiguous data retrieval with the returned fields enumerated. It does not, however, distinguish itself from siblings like buy_crypto_price or the buy_coin_*/buy_tok_* families, so an agent cannot tell from the text alone why it should pick this token-scoped endpoint.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many price-related siblings (buy_crypto_price, buy_coin_*, buy_tok_*). The only contextual cues are commercial ('Paid', '$0.05 USDC on Base or Solana'), which inform cost but not selection. An agent must infer usage from the tool name alone.

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