Skip to main content
Glama

SouthPow crypto & market data

buy_coin_S

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

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

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, the description carries the full load and does well: it discloses the pay-per-call price ($0.01 USDC on Base), that no account or API key is required, that failed calls are not charged, and which upstream venues the data comes from (Coinbase Exchange with Kraken cross-check). It does not state latency or data freshness, and the 'Paid.' prefix is terse about the payment flow mechanics.

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?

Dense, front-loaded, and every fragment carries information — paid status first, then the data payload, then cost, prerequisites, and URL. It reads as telegraphic notes rather than prose, which slightly hurts scannability but wastes almost nothing.

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 price endpoint, the description supplies the returned fields, the commercial cost, the auth-free access model, and the upstream sources — enough to decide and invoke confidently. The absence of data-freshness/latency info is the only meaningful gap for a live price tool.

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 no parameter meaning to add; the baseline applies. The description instead spends its words on output fields and prerequisites, which is the right allocation for a parameterless endpoint.

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?

States the resource precisely (S/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. The token symbol in the title plus the pair name makes clear which sibling variant this is, though it never explicitly says 'for the S token only' — an agent must infer that from the symbol.

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 a per-coin quote lookup, and the symbol identifies the scope. There is no explicit guidance about when to pick this over the general sibling buy_crypto_price or how it differs from other exchange-source siblings, so an agent must infer the selection rule from the tool name alone.

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