Skip to main content
Glama

SouthPow crypto & market data

buy_tok_QKA

Paid. Qkacoin (QKA) 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/QKA.

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

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?

No annotations are supplied, so the description carries the full load, and it does well: it discloses that the call is paid, the exact cost ($0.01 USDC), the accepted chains (Base or Solana), that no credentials are required, and that failed calls are not billed. Remaining gaps are rate limits, latency/staleness of the quote, and the shape of the response, 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.

Conciseness5/5

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

Six terse fragments, each carrying distinct information: payment flag first, then the payload, then cost/rails, then auth and billing terms, then the endpoint. Nothing is repeated and the most decision-critical fact (that it costs money) is front-loaded.

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 tool with no output schema, the description is close to self-sufficient: it enumerates the returned fields, the price, the payment rails and the failure-billing policy. It stops short of describing the response format or data freshness, which matter somewhat given there is no output schema to fall back on.

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 and the input schema is an empty object, so there is no parameter meaning for the description to add. This is the baseline 4 case; the token is baked into the tool itself and is already stated in the description.

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 dataset: Qkacoin (QKA) with live USD price, 24h change and market-cap rank. An agent knows exactly what data comes back. It falls short of a 5 because it never differentiates itself from the large sibling families doing similar work (buy_coin_*, buy_crypto_price), so an agent still has to infer why buy_tok_QKA exists alongside them.

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 only implied: it is a paid single-token price lookup, and the payment/auth notes (no account, no API key, failed calls free) help an agent decide whether to spend. There is no explicit when-to-use or when-not-to-use statement and no named alternative such as buy_crypto_price or the buy_coin_* equivalents.

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