Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PRESPCX

Paid. SpaceX (Republic Pre-IPO) (PRESPCX) 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/PRESPCX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: a $0.01 USDC charge on Base or Solana, no account or API key required, and a stated failure policy (failed calls not charged). It omits the response format, latency, and whether the quoted price is cached or real-time.

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?

A single dense sentence with payment terms first, then data returned, then cost, then failure policy, then the endpoint URL. No filler and no repetition; everything an agent needs 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, no-output-schema price lookup, the description covers what is sold, the price and payment rails, the no-auth requirement, failure billing, and the returned fields. The main remaining gap is the concrete response shape, which is left unstated since no output schema exists.

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 clarify beyond the schema. The description correctly implies the asset is baked into the endpoint via the URL path, matching the empty input schema.

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 specific asset (SpaceX Republic Pre-IPO, ticker PRESPCX) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It does not, however, distinguish this tool from the many near-identical siblings (buy_tok_SPCX, buy_tok_RSPCX, buy_tok_SPCXX, buy_tok_SPCXON), so an agent must infer the difference from the ticker alone.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as buy_crypto_price or the other SpaceX-ticker tools. The only context is a price tag and payment method, which tells the agent how to pay but not when this tool is the right pick over its siblings.

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