Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SATS

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

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

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 burden and does well: it discloses cost ($0.01 USDC), payment chains (Base or Solana), that no authentication is required, that failures are not billed, and the backing endpoint URL. It stops short of rate limits or response shape beyond the three named fields.

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?

Front-loaded and dense — 'Paid.' appears first, then purpose, price, access terms, and URL, with no filler. The telegraphic fragments ('Paid.', 'No account, no API key.') are efficient but slightly clipped rather than fully structured prose.

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, output-schema-less price tool, the description supplies the returned fields, the cost, the payment rails, and the auth requirements — enough to call it correctly. Lacking only finer output formatting and rate-limit behavior, which are minor for this complexity.

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 has nothing to explain and the baseline of 4 applies. The description adds nothing extraneous about inputs, which is correct here.

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 asset (SATS / Ordinals SATS) and the exact payload — live USD price, 24h change, market-cap rank — so an agent can tell what it returns without opening anything else. It does not explicitly name the verb (fetch/buy a price snapshot), relying on the 'buy_' prefix, which keeps it just short of a 5.

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: the reader infers 'call this to get SATS price data.' The description adds useful access conditions (paid, no account, no API key, failed calls not charged) but gives no when-not guidance and never routes to alternatives such as buy_crypto_price or the other tok_* siblings for different assets.

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