Skip to main content
Glama

SouthPow crypto & market data

buy_tok_QTUM

Paid. Qtum (QTUM) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/QTUM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the $0.01 USDC charge on Base or Solana, that no credentials are needed, and that failed calls are not billed — critical behaviors for a paid endpoint. It stops short of rate limits, caching/freshness, or what an error response looks like, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the paid flag and the data returned, then pricing, auth, billing, and endpoint. Every clause carries distinct operational information with no filler.

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 parameterless, single-asset paid price lookup with no output schema, the description covers the return fields, cost, payment rails, and billing guarantee — enough to call it correctly. Minor gaps are data freshness and error semantics, which an agent might want for a metered call.

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?

There are zero parameters, so the baseline is 4; the description correctly implies no input is required beyond the call itself. Nothing in the text contradicts or complicates the empty schema.

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 concrete resource and scope: Qtum (QTUM) live USD price, 24h change, and market-cap rank, plus the explicit 'Paid' marker. It does not, however, distinguish itself from adjacent siblings such as buy_crypto_price or the buy_coin_* family, so an agent cannot resolve choosing between them from this text alone.

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?

It gives useful invocation context (cost, accepted payment chains, no account or API key required) that implies 'call this when you need a paid QTUM quote without auth'. There is no explicit when-to-use versus when-not guidance, and no mention of the free-looking alternatives in the sibling set.

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