Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CTR

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

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

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?

No annotations are supplied, so the description carries the full burden and does most of it well: it declares the tool is paid, states the exact price ($0.10 USDC on Base), the payment rail, that no account or API key is required, and that failed calls are not charged. It omits rate limits, latency, and data freshness/delay, which matter for a market-price 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?

It is dense and front-loaded with the most decision-relevant fact ('Paid.'), and every clause conveys pricing, coverage, or provenance. The raw endpoint URL is slightly promotional overhead but still plausibly useful for payment/prepay flows.

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?

With no annotations and no output schema, the description compensates by enumerating the returned fields and naming the upstream sources (Coinbase Exchange, Kraken cross-check), which is the key missing piece. Data freshness and failure/error shape are the remaining gaps for a zero-parameter paid tool.

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 schema has nothing to explain and the baseline is 4. The description usefully clarifies that no auth or API-key parameter is needed, confirming the call is fully determined by the tool name.

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 the exact resource (CTR/USD) and enumerates the data points returned: last price, 24h open/high/low, % change, 24h and 30d volume. The verb is implied rather than stated, but the symbol-in-name convention across the buy_coin_* family makes the scope unambiguous.

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 symbol in the name, and the cost/no-account/no-charge-on-failure notes help the agent decide whether to spend. However, it never addresses the obvious alternative, the sibling buy_crypto_price, nor does it say when this paid endpoint should be preferred over a free or generic price 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