Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CTX

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

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

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, the description carries the full burden and largely meets it: it discloses the cost ($0.002 USDC on Base), the payment rail, that no credentials are needed, and that failed calls are not charged. It does not describe the response shape/pagination or how payment is actually settled, which keeps it from 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?

Telegraphic but front-loaded: cost first, then the data payload, then access terms and endpoint URL. Every clause carries information; the only mild cost is the dense comma-splicing, which is acceptable for this length.

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, annotation-free, output-schema-free paid endpoint, the description supplies the fields returned, the source exchanges, price, access requirements, failure policy, and the URL. An agent has enough to decide and invoke; only the exact response envelope is unspecified.

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; the description correctly implies the call is parameterless and fully determined by the tool name. No schema semantics are needed or missing.

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 specific resource and fields precisely: 'CTX/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus the two data sources (Coinbase Exchange, Kraken cross-check). That is far more than the name 'buy_coin_CTX' conveys. It does not explicitly differentiate from the 500+ ticker siblings or from buy_crypto_price, but the ticker-scoped enumeration makes the distinction inferable.

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 ticker scope and by stating access conditions ('No account, no API key'), which tells the agent it can call freely. However, there is no explicit when-to-use/when-not guidance and no reference to alternatives such as buy_crypto_price, which likely overlaps.

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