Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KNTQ

Paid. Kinetiq (KNTQ) 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/KNTQ.

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

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, the description carries the full burden and does so well: it states the tool is paid, the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. The only real gap is rate limits and any caching/TTL behavior. This is substantially more behavioral context than most paid-tool descriptions provide.

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?

Extremely compact and front-loaded: 'Paid.' comes first, then the data delivered, then cost and payment rails, then the failure policy and endpoint. Every fragment 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 zero-parameter, no-annotations, no-output-schema tool, the description covers what is returned, what it costs, how it is paid for, and that failures are free. Left unstated are the response encoding/format and whether results are cached, which are minor for a single-asset price lookup but not fully negligible.

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 and there is nothing for the description to disambiguate. The fixed endpoint URL is disclosed, which reinforces that no per-call arguments are supplied.

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 exact token (Kinetiq/KNTQ) and enumerates the returned data: live USD price, 24h change, market-cap rank. It is a data-retrieval tool stated without an explicit verb, but the payload it produces is unambiguous and the token-specific name separates it from the hundreds of buy_tok_* siblings.

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: an agent needing KNTQ pricing will recognize this as the tool. There is no statement of when to prefer it over buy_crypto_price or other price tools, and no exclusion (e.g., whether it covers historical prices). The payment terms do help the agent decide whether invoking is worth the cost, which nudges it above pure inference.

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