Skip to main content
Glama

SouthPow crypto & market data

buy_coin_QI

Paid. QI/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/QI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 does substantial work: it discloses the payment model ($0.25 USDC on Base), that no auth is required, and that failed calls are not charged — exactly the operational facts an agent needs before invoking a paid endpoint. It stops short of stating rate limits or response format, but the field list partially covers the latter.

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?

The description is compact and front-loads both the paid nature ('Paid.') and the core data payload. The raw URL at the end is slightly noisy for an MCP context and the opening 'Paid.' is terse to the point of being cryptic, but no sentence is wasted.

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?

There is no output schema, so the description usefully enumerates the returned fields and their sources, which is the key missing structured information. Pricing, auth, and failure semantics are also covered, leaving only minor gaps like response encoding and staleness/freshness guarantees.

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; baseline is 4. The description correctly implies no arguments are needed by framing the call as a fixed QI/USD lookup with an embedded URL.

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 a concrete resource and scope: QI/USD live price with explicit fields (last, 24h open/high/low, % change, 24h/30d volume) and data sources (Coinbase Exchange, Kraken cross-check). It is clearly distinguishable from other buy_coin_* siblings by the QI designation, though it never contrasts itself with buy_crypto_price, which appears to cover similar ground.

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?

It discloses prerequisites (no account, no API key, paid $0.25 USDC on Base) but gives no when-to-use guidance and no comparison to alternatives such as buy_crypto_price or other coin-specific tools. An agent must infer that this is the QI-specific price lookup rather than a purchase tool, since 'buy_coin' suggests a transaction.

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