Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SPCXX

Paid. SpaceX xStock (SPCXX) 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/SPCXX.

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

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 at all, the description carries the full burden and does most of it well: it discloses the $0.01 USDC cost, accepted chains (Base or Solana), absence of auth, the failed-call refund policy, and the underlying URL. Missing is any statement about response shape or data freshness, which is the remaining behavioral gap for a paid call.

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?

Three terse sentences, front-loaded with 'Paid.' so cost is the first thing the agent sees, and every clause carries information (subject, fields, price, rails, auth, refunds, URL). The telegraphic style borders on cryptic but does not waste words.

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 no-parameter, no-output-schema paid endpoint this is close to complete: cost, payment method, auth requirements, partial-refund behavior, and the three returned fields are all stated. The only shortfall is that sibling ticker variants are never differentiated and the return format is described only in prose terms.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The asset ticker is fixed in the tool name, which is consistent with the empty 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?

Names the exact asset ('SpaceX xStock (SPCXX)') and enumerates what is returned: live USD price, 24h change, and market-cap rank, so an agent knows precisely what it is buying. It does not, however, distinguish SPCXX from the near-identical siblings buy_tok_SPCX, buy_tok_SPCXB, buy_tok_SPCXON, or buy_tok_RSPCX, which is a real disambiguation gap in this namespace.

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?

Gives useful preconditions in 'No account, no API key' and 'Failed calls not charged', plus the payment rails, so an agent knows it can call this without setup. But it never says when to prefer this over buy_crypto_price or one of the SPCX-variant siblings, so the usage decision is left implied.

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