Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SPCX

Paid. SpaceX (Backpack Securities) (SPCX) 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/SPCX.

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

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, the description carries the full load and does it well: it discloses the price ($0.01 USDC), the accepted payment rails (Base or Solana), that no account or API key is required, that failed calls are not charged, and the underlying endpoint URL. It stops short of describing response format, data freshness/latency, or rate limits, which keeps it from a 5.

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?

Information is front-loaded ('Paid.' then the data delivered, then cost, then access requirements), and every sentence carries distinct value. Slightly dense parenthetical stacking ('SpaceX (Backpack Securities) (SPCX)') and the trailing bare URL cost it a perfect score.

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 tool, the definition covers what an agent needs to decide and pay: the data returned, the price, the payment networks, the no-account access model, and the failure policy. Missing freshness/latency and response shape are minor for a simple price endpoint.

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 no parameter meaning to add; baseline 4 applies. The description correctly avoids inventing parameter discussion and instead spends its words on cost and payment mechanics.

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 verb/resource outcome: live USD price, 24h change and market-cap rank for SPCX (SpaceX / Backpack Securities). An agent can tell it is a paid price-lookup without opening the schema. It does not, however, distinguish this from the near-identical siblings buy_tok_SPCXX, buy_tok_SPCXB, buy_tok_SPCXON, or buy_coin_SPX, so sibling differentiation is only partial.

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 by the 'Paid' framing and the stated cost, and the agent learns that failures are not charged. But there is no explicit when-to-use / when-not-to-use guidance and no routing to the many alternative SPCX-related tools in the sibling list, which is the main ambiguity an agent faces here.

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