Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CELR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 load and does well: it discloses the price ($0.01 USDC on Base), the absence of account/API-key requirements, the failure policy ('Failed calls not charged'), the upstream sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It stops short of rate limits, latency, or cache/TTL behavior, which matters for a paid per-call tool.

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?

Telegraphic and front-loaded – 'Paid.' leads so cost is the first thing the agent sees, followed by payload, then commercial terms, then the URL. Every clause is informative; the only minor cost is the dense, list-like punctuation that reads as a spec sheet rather than prose.

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, no-output-schema tool, the description covers nearly everything an agent needs: what comes back, what it costs, how to pay, that no auth exists, and that failures are free. Rate limits and exact response shape are the remaining gaps, but the enumerated fields largely compensate.

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 the baseline is 4 and there is nothing further for the description to clarify. The description correctly adds no parameter guidance it does not need.

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 names a specific resource and payload: 'CELR/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. An agent immediately knows this is a single-asset spot-price snapshot, distinct from the many other buy_coin_* siblings purely by the CELR symbol scope.

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 asset scope and the field list, and the cost line tells the agent a call is a paid transaction. However, it never says when to prefer this over a broader sibling such as buy_crypto_price, nor does it state any preconditions or exclusions.

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