Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RSPCX

Paid. SpaceX Tokenized Stock (Reality) (RSPCX) 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/RSPCX.

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

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?

With no annotations, the description carries the full burden and does disclose real behavior: it is a paid call at $0.01 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It also enumerates the returned fields (price, 24h change, market-cap rank). What is missing is freshness/latency of the price and whether the quoted price is executable or indicative.

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 with 'Paid.' then the payload, cost, access terms and endpoint in four short clauses with no filler. The raw URL is somewhat redundant inside an MCP tool listing, and 'No account, no API key' restates the same idea twice, but overall it is tight.

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 price lookup with no output schema, the description covers what the agent needs: cost, accepted chains, billing on failure, and the shape of the result. Only price staleness and whether the value is a live quote versus a cached snapshot remain unstated.

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 schema is empty and correctly so for a fixed-asset price lookup.

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 resource and payload: SpaceX tokenized stock (RSPCX) price with live USD price, 24h change and market-cap rank. The ticker plus 'tokenized stock (Reality)' identifies the asset, but with siblings like buy_tok_SPCX, buy_tok_SPCXB, buy_tok_SPCXX, buy_tok_SPCXON and buy_tok_PRESPCX in the same family, the description does not explain how this variant differs from those near-identical names.

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 when-to-use or when-not guidance, and no routing among the many SpaceX-adjacent sibling tools. The only conditional information is operational (payment, billing), not selection guidance, so the agent must infer usage entirely from the ticker in the name.

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