Skip to main content
Glama

SouthPow crypto & market data

buy_tok_QQQX

Paid. Nasdaq xStock (QQQX) 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/QQQX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 cost, accepted payment chains, the absence of auth, and the refund policy for failed calls, which is exactly the risk information an agent needs before spending. The gap is operational mechanics — how payment is actually attached to the call and what a failure looks like — plus no hint of the response shape beyond the three quoted fields.

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?

Front-loaded and dense: price and fields first, then cost, payment rails, auth posture, billing policy, and the endpoint URL. The telegraphic fragments ('Paid.', '$0.05 USDC on Base or Solana.') read well for scanning, though the URL at the end is dead weight for an agent that invokes the tool rather than fetching it.

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-output-schema paid endpoint, the description covers what the agent must decide: what data it returns, what it costs, how to pay, and that failures are free. It stops short of describing the response envelope or freshness/latency of the 'live' price, which matters for a pricing call but is the only real omission.

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 and the schema is trivially complete. The description correctly spends no space on parameters and instead documents cost and transport, which is the meaningful variable here.

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?

States a specific verb and resource: live USD price for the Nasdaq xStock QQQX, plus 24h change and market-cap rank. The ticker scope is unambiguous against the alphabet soup of buy_tok_* siblings, but it never names the obvious generic alternative (buy_crypto_price) so the agent must infer that this is the per-token variant.

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 implied rather than stated: an agent gathers that this is for QQQX price data, and the payment prerequisites ($0.05 USDC on Base or Solana, no account or API key, no charge on failure) are spelled out. There is no explicit when-to-use-vs-alternative guidance, e.g., no guidance on whether to prefer buy_crypto_price or a different xStock ticker such as QQQON.

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