Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SOON

Paid. SOON (SOON) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/SOON.

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

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, the description carries the full behavioral burden, and it does a good job disclosing that the call is paid ($0.05 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged — the failure/charging policy is exactly the kind of detail an agent needs before a spend. It omits data freshness/latency and rate limits, which keeps it below 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?

Five short clauses, front-loaded with what the call returns, then cost, then prerequisites, then the failure policy, ending with the endpoint URL. It is telegraphic and dense with no filler, though the bare "URL https://..." fragment is slightly raw in style.

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, no-annotation paid endpoint, the description covers the essentials: what data returns, what it costs, which chains/currencies are accepted, that no auth is needed, and that failures are free. Only return-format details (JSON shape, units, timestamp of the quote) are absent, which is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4, and the description correctly adds no parameter noise while making clear the call is fully self-contained (no symbol argument, no key). Nothing is left ambiguous about how to invoke it.

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 and payload: "SOON (SOON) price: live USD price, 24h change and market-cap rank," which is a specific resource plus enumerated returned fields. It does not, however, differentiate itself from the hundreds of sibling quote tools (buy_coin_*, buy_crypto_price), so an agent must infer that buy_tok_SOON is the SOON-specific variant.

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 rather than stated: it is evidently the tool for SOON spot price data, and the payment terms establish preconditions for calling it. There is no explicit when-to-use/when-not guidance and no named alternative, which matters given siblings like buy_crypto_price and buy_coin_X that could plausibly cover similar data.

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