Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN19

Paid. Blockmachine (SN19) 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/SN19.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 burden and does well: it discloses the cost, the accepted payment rails, the absence of authentication, and the failure-charge policy ('Failed calls not charged'). It stops short of stating rate limits or response shape beyond the field list, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short fragments, each carrying distinct information: payment status, payload, price and rails, auth and billing behavior, endpoint. Nothing is repeated from the name and nothing could be cut without losing a fact.

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-argument paid lookup with no output schema, the definition covers what the agent most needs: what comes back, what it costs, and that failures are free. The only real gap is that the exact response structure is unspecified, since no output schema backs it up.

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 usefully confirms that the asset is baked into the endpoint rather than passed in.

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?

Names the specific resource (Blockmachine / SN19) and enumerates the payload: live USD price, 24h change, market-cap rank. That is enough to distinguish it from most siblings, but it never explains how it relates to the near-identical buy_coin_* or buy_crypto_price tools in the catalog.

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?

It gives the practical prerequisites for calling it — paid, $0.05 USDC on Base or Solana, no account or API key — which is real usage context. However, it offers no when-to-use guidance relative to the hundreds of alternative price tools (buy_coin_SN19-style entries, buy_crypto_price), leaving sibling selection to inference from the 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