Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SPK

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavioral burden and does well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, is not charged on failure, and cross-checks Coinbase Exchange against Kraken. The main omission is what the failure mode or payment handshake looks like from the caller's side (e.g. whether a 402 must be handled), which matters for an agent orchestrating 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?

Extremely dense and front-loaded: cost first, then payload, then data sources, then access terms, then endpoint. The telegraphic style ('Paid. SPK/USD live: ...') reads slightly like a price tag rather than prose, but every clause carries information and nothing is wasted.

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?

With no output schema, the description enumerates the returned fields well enough for an agent to know what it will get back, and payment and auth requirements are covered. Remaining gaps are the exact response shape (units, timestamps, JSON keys) and error behavior, which are moderate but not blocking for a fixed-purpose read 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 the schema baseline is 4. The description correctly implies a fixed, parameter-free endpoint by embedding the fully-qualified URL, leaving nothing for the agent to infer about inputs.

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 states a concrete resource and payload: live SPK/USD price with last, 24h OHLC, % change, and volume. It is distinguishable from generic siblings only through the token named in the text, since the ~400 sibling buy_coin_* tools share the same shape; the description does not explicitly frame itself as 'the SPK variant of the family', but the ticker plus field list makes retrieval intent unambiguous.

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 guidance on when to call this versus buy_crypto_price or a sibling token tool, no statement about refresh cadence or staleness, and no when-not-to-use condition. The agent must infer that this is the correct tool purely from the ticker in the name and the SPK in the description.

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