Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NEO

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

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

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, the description carries the full burden and does well: it discloses that the call is paid, the exact cost and accepted chains (Base or Solana), that no credentials are required, and crucially that 'Failed calls not charged', which is the main risk an agent cares about for a metered call. What it omits is the mechanics of the payment handshake and any rate limit.

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?

Extremely dense and front-loaded — cost and payment terms precede the data description, which is the right priority for a paid endpoint. Every clause carries information; the raw endpoint URL is the only element of marginal value to an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, fixed-asset price lookup with no output schema, the description covers the returned fields (USD price, 24h change, market-cap rank), the price, payment rails, auth-free access, and failure billing. That is everything an agent needs to decide and call correctly.

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; the schema is empty and 100% described. Baseline 4 applies, and the description correctly implies no filtering or symbol argument is needed because the token is fixed by the tool name.

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: 'NEO (NEO) price: live USD price, 24h change and market-cap rank', which tells an agent exactly what data comes back. It does not distinguish itself from the near-identical sibling buy_coin_NEO, so an agent facing both must guess which price endpoint to call.

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?

The leading 'Paid.' plus the $0.05 USDC price gives a clear cost-based precondition for using it, and 'No account, no API key' removes setup friction. However, there is no guidance on when to prefer this over buy_crypto_price or buy_coin_NEO, and no exclusions.

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