Skip to main content
Glama

SouthPow crypto & market data

buy_tok_QKC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 well: it discloses the price ($0.05 USDC), the accepted chains (Base or Solana), that no credentials are needed, that failed calls are not charged, and gives the endpoint URL. What it does not explain is the payment mechanism itself — with zero input parameters there is no visible field for how the $0.05 is settled, which is a notable omission for a paid tool.

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?

Roughly forty words delivered as terse, front-loaded clauses: purpose first, then price, then prerequisites, then failure policy, then URL. Nothing is redundant and nothing buries the lede.

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 paid lookup, the description covers what is returned, what it costs, on which chains, and that failures are free — enough for an agent to decide and call. The remaining gap is the mechanics of payment authorization, which the schema cannot express since it declares no properties.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies the call is fully determined by the tool name (fixed ticker QKC) rather than by inputs.

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 the exact asset (QuarkChain / QKC) and the exact payload (live USD price, 24h change, market-cap rank), so an agent can tell it apart from the hundreds of sibling buy_tok_* tickers without opening anything else. The leading 'Paid.' also sets the transactional nature of the call immediately.

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 implies the use case (fetch QKC spot stats) and states prerequisites — no account, no API key — but never names an alternative such as buy_coin_QKC, buy_tok_Q, or buy_crypto_price, nor says when this paid call is preferable to a free generic price lookup. Usage is inferable rather than guided.

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