Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TQQQB

Paid. ProShares UltraPro QQQ (bStocks Tokenized Stock) (TQQQB) 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/TQQQB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does a good job on the commercial surface — $0.01 USDC on Base or Solana, no account or API key, failed calls not charged, plus the direct URL — but says nothing about rate limits, price freshness/latency, or what happens on a successful partial response.

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?

The text is short and front-loaded: the paid flag and the asset identity come first, then the payload, then cost and access terms. The echoed URL and the parenthetical '(TQQQB)' restate information already in the tool name, which is mildly redundant but not wasteful.

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-annotation, no-output-schema price lookup, the description covers everything an agent needs to decide and call: what data comes back, what it costs, how to pay, that failures are free, and the underlying endpoint. The main omission is price staleness, which matters for a live market quote.

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 a 4; there are no inputs whose meaning needs explaining in prose. The description correctly implies the ticker is baked into the endpoint rather than passed as an argument.

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 specific resource (ProShares UltraPro QQQ tokenized stock, ticker TQQQB) and enumerates the exact data returned: live USD price, 24h change, market-cap rank. It does not, however, distinguish this from the hundreds of near-identical buy_tok_* siblings (e.g. buy_tok_QQQON, buy_tok_QQQX) beyond the ticker itself, so the agent must rely on the name to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage framing is implicit: it is cheap, paid per call, and needs no account. There is no statement of when to choose this over a generic sibling like buy_crypto_price or another tokenized-equity tool, and no exclusions or prerequisites are given.

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