Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SPYX

Paid. SP500 xStock (SPYX) 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/SPYX.

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

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 well: it discloses the cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is required, that failed calls are not charged, and the concrete endpoint URL. It stops short of explaining how payment is actually settled (e.g. whether an x402 challenge round-trip occurs) or what happens on repeated calls.

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?

It is compact and front-loaded with the most decision-relevant fact ('Paid'), followed by payload, price, access terms and endpoint. The telegraphic style ('URL https://...') is slightly clipped but every sentence carries information an agent needs before spending money.

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, single-endpoint paid data tool with no output schema, the description supplies cost, payment rails, access requirements, failure policy and the returned fields — enough to call correctly. It could be fuller only on the payment flow mechanics, which is a minor gap given the tool's simplicity.

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 disambiguate; the baseline of 4 applies. The description correctly implies no input is needed beyond the call itself.

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 resource (SP500 xStock ticker SPYX) and exactly what data comes back: live USD price, 24h change and market-cap rank. It is distinguishable from the mass of buy_coin_* and buy_stable_* siblings, though it does not explain how buy_tok_SPYX differs from adjacent siblings like buy_tok_SPY, buy_tok_SPYB or buy_tok_SPYON, which an agent would have to infer 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 Guidelines3/5

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

Usage context is implied rather than stated: 'Paid' plus the price tag signals this is only worth calling when an agent needs SPYX market data and is willing to spend $0.01. There is no explicit when-to-use / when-not-to-use guidance and no named alternative (e.g. buy_crypto_price), so the agent must derive selection logic from the ticker.

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