Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CP

Paid. CP/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CP.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value: explicit price ($0.25 USDC on Base), no auth requirement, and the refund policy for failed calls. However, it omits rate limits, latency, response shape/units, and what counts as a 'failed' call, so an agent cannot fully predict the outcome of a paid invocation.

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 compact and front-loaded, leading with 'Paid.' and the exact payload, then cost, auth, and billing terms. Slightly telegraphic phrasing ('% change' without a period qualifier) and the bare endpoint URL are the only minor inefficiencies.

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 paid endpoint with no output schema and no annotations, the description covers cost, payment chain/currency, auth requirements, billing on failure, data fields, and upstream sources. The main residual gap is not enumerating return-value format, which is partly mitigated by listing the metrics returned.

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 schema is empty and fully covered. The description correctly adds no parameter commentary, which is appropriate here.

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 states a concrete resource and payload: 'CP/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', with named data sources (Coinbase Exchange, Kraken cross-check). It does not explicitly say how it differs from sibling buy_coin_* tools or from buy_crypto_price, relying on the token suffix in the name to carry that distinction.

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 when-to-use or when-not-to-use guidance and no pointer to alternatives such as buy_crypto_price or get_schema, despite a very large sibling set. Only indirect context is given (paid, no account/key, failed calls not charged), which helps an agent decide whether invoking is acceptable but not whether it is the right tool.

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