Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SPA

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

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

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 supplied, the description carries the full disclosure burden and does a solid job: it states the tool is paid ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, and that the data comes from Coinbase Exchange with a Kraken cross-check. What it omits is the mechanics of the paid call (how payment is submitted, whether the URL is the payable endpoint) and the response format, which matters given there is no output schema.

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?

Eight short fragments, front-loaded with the paid status and the data payload, then the non-functional details (price, credentials, SLA, endpoint). Nothing is padded, though the telegraphic style ('Paid.') sacrifices a little readability for density, and the trailing raw URL is somewhat unpolished.

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 parameterless, single-purpose data tool with no output schema, the description supplies enough: the returned fields are enumerated, the upstream sources are named, and the payment/credential model is spelled out. The main residual gap is response shape (JSON? field names? latency?), which an agent would need to actually use the output.

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 and the baseline of 4 applies. The description correctly implies a parameterless single-asset lookup, and the embedded URL confirms the asset is fixed in the endpoint rather than passed as an argument.

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 (SPA/USD) and enumerates the fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. That is far more specific than the bare ticker name, and it clearly separates this tool from the hundreds of other buy_coin_<ticker> siblings. It loses a point only because the phrasing is a noun fragment with no explicit verb (fetch/retrieve), so the action must be inferred.

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 only implied: an agent can infer this is the tool for live SPA spot pricing. There is no statement of when to prefer it over sibling price tools such as buy_crypto_price or buy_pm_crypto, and no exclusions or preconditions beyond the payment note. The 'Paid. $0.05 USDC on Base' line hints at a cost trade-off but never tells the agent when that trade-off is worth it.

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