Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SPX

Paid. SPX/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/SPX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the cost, that no credentials are needed, that failed calls are not billed, the data provenance (Coinbase Exchange with Kraken cross-check), and the backing endpoint URL. It does not describe the response shape or any 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegraphic but front-loaded: the paid flag comes first, then the payload, then price/access terms. Every fragment carries information (cost, sources, credential-free access, billing policy), with no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter paid data lookup with no output schema, the description covers everything an agent needs to decide and call: what data comes back, what it costs, that no auth is needed, and that failures are free. The endpoint URL even supports direct invocation rationale.

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 a call with no arguments, 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?

The description names the exact resource (SPX/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It is specific about scope, but it never states the verb/action or explicitly contrasts itself with per-coin siblings or with the generic buy_crypto_price tool, relying on the tool name for that differentiation.

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?

Payment terms ('$0.002 USDC on Base', 'No account, no API key', 'Failed calls not charged') give useful preconditions for calling it, and 'Paid' flags the cost model up front. However, there is no guidance on when to choose this over the sibling buy_crypto_price or another asset's buy_coin_* tool, so the usage decision is left implicit.

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