Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN34

Paid. BitMind (SN34) 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/SN34.

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

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 that the call is paid ($0.01 USDC), settlement chains (Base or Solana), that no auth is needed, and that failed calls are not charged. It leaves unstated what a payment failure or partial failure looks like and gives no rate-limit or latency context, keeping it out of 5 territory.

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?

Terse and front-loaded — 'Paid.' leads, then what is returned, then cost/rails, then the failure-billing caveat and endpoint URL. Every clause carries distinct information; the telegraphic fragments are slightly clipped but not wasteful.

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?

With no output schema, the description must state the return contents, and it does (live USD price, 24h change, market-cap rank). It also covers cost, payment rails, and auth expectations, which is what an agent needs before spending money. Response shape details such as field names or freshness timestamp remain unspecified.

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 (empty object schema, none required), so there is no per-parameter meaning to add. The description correctly avoids inventing inputs and notes the fixed URL endpoint, which is the right baseline for a parameterless tool.

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 a specific resource and payload: 'BitMind (SN34) price: live USD price, 24h change and market-cap rank.' That is far more than a restatement of the name and lets an agent distinguish SN34 from the SN107/SN110 siblings. It does not explicitly name an alternative, so it stops 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 implied by the payload description — call this to obtain SN34 price data — and the 'No account, no API key' line removes a common prerequisite question. There is no explicit when-to-use versus when-not, and no routing guidance against near-neighbours like buy_crypto_price or buy_tok_SN3.

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