Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ATONE

Paid. AtomOne (ATONE) 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/ATONE.

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

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 a good job: it discloses that the call is paid, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It stops short of stating rate limits, latency, or whether payment is collected before or after the response, so it is not fully comprehensive.

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?

Front-loaded with 'Paid.' followed by the resource and its return fields, then cost, chain, auth, failure policy, and URL as terse fragments. Every clause conveys a distinct, actionable fact with no filler or repetition.

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 lookup, the description covers what is returned, what it costs, how to pay, and the failure-charging policy. Missing only response shape/format details and any statement of freshness or rate limits, which are minor for this tool's 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 input schema has zero parameters, so the baseline is 4. There are no parameter semantics to add or omit, and the description correctly does not invent any inputs.

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 a specific resource (AtomOne / ATONE price) and enumerates exactly what comes back: live USD price, 24h change, and market-cap rank. An agent can tell what it fetches without opening the schema. It does not, however, distinguish this endpoint from the many sibling buy_coin_<SYMBOL> and buy_crypto_price tools, so the sibling boundary is left implicit.

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 context is implied by 'No account, no API key' and the price/payment detail, which signals a self-serve paid lookup. There is no explicit statement of when to choose this over buy_coin_ATOM or buy_crypto_price, and no exclusions or alternatives named. Adequate but leaves routing to inference.

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