Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SUKU

Paid. SUKU/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/SUKU.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose key behavioral traits: it is paid ($0.05 USDC on Base), requires no account or API key, failed calls are not charged, and data comes from Coinbase Exchange with a Kraken cross-check. It omits any description of response shape or staleness/latency guarantees, 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?

Information is front-loaded with the critical 'Paid.' flag and cost, followed by the data payload and access terms. It is dense but every clause carries signal; no filler sentences.

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, annotation-free, output-schema-free paywalled data tool, the description covers cost, payment rail, access requirements, upstream sources, and returned fields. Only the exact response format and error behavior remain unstated, a modest gap.

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 parameter semantics default to the 4 baseline; there is nothing for the description to clarify beyond the fixed URL endpoint it supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (SUKU/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, with named sources. An agent can tell precisely what this tool provides and distinguish it from the other buy_coin_* siblings by the pair in the name.

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?

The description establishes prerequisites (paywall, no account/API key needed) but never states when to use this tool versus alternatives such as buy_crypto_price or another coin's tool. Usage is implied by the coin-specific name rather than explicitly guided.

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