Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CC

Paid. Canton (CC) 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/CC.

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

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 substantial work: it discloses that the call is paid, the exact cost ($0.05 USDC) and accepted chains (Base, Solana), that no account or API key is needed, and that failed calls are not charged. Missing are rate limits, latency, and any caching or freshness caveat, 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?

Five short sentences, front-loaded with the critical fact ("Paid.") followed by purpose, price, friction, and failure policy. Minor redundancy in "Canton (CC) price: live USD price" and an endpoint URL that duplicates what the tool name already encodes, but nothing is padded.

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 read tool with no output schema, the description covers what an agent needs to commit: what data comes back, what it costs, how to pay, and that failures are free. The one omission relative to this tool's actual complexity is sibling routing across an enormous catalogue of near-identical price tools.

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 input schema declares zero parameters at 100% coverage, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool is 4. The description correctly takes no arguments and instead spends its words on payment and behavior, which is the right allocation.

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?

"Canton (CC) price: live USD price, 24h change and market-cap rank" names the specific resource and the exact payload the agent gets back, which is far better than a bare name restatement. It does not, however, distinguish this from the many siblings that also serve price data (buy_crypto_price, the buy_coin_* and buy_tok_* families), so an agent must infer selection from the ticker alone.

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 rather than stated: "Paid" plus a concrete price and payment rails signals this is a pay-per-call quote rather than a free lookup. There is no explicit when-to-use or when-not-to-use guidance and no named alternative, which is a real gap given a sibling list containing hundreds of price-related tools.

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