Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NEON

Paid. NEON/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/NEON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does disclose the key behavioral facts: $0.05 USDC on Base, no auth required, no charge on failure, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and data freshness guarantees, which matter for a paid per-call endpoint.

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-loads 'Paid.' then the data payload, then pricing/auth terms, then the URL. Telegram-style fragments are efficient and every clause carries information. It is slightly dense and would read better with a clear sentence on the return payload.

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-param paid GET endpoint with no output schema, the definition covers cost, auth, failure billing, sources, and the returned fields. The main remaining gap is that it never states the response shape or freshness, and the 'buy' naming versus data-fetch behavior could confuse an agent.

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 is 4. The description usefully clarifies that the symbol and quote currency are fixed in 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?

The description states a specific resource and scope: a NEON/USD live price snapshot with last price, 24h open/high/low, percent change, and 24h/30d volume. That is far more concrete than the bare tool name, which merely says 'buy_coin_NEON'. It does not, however, distinguish this from the hundreds of sibling buy_coin_* tools or from buy_crypto_price.

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 useful calling context (paid, no account, no API key, failed calls not charged) that implies when a call is safe to make. It never says when to prefer this over buy_crypto_price or the other per-coin siblings, and gives no exclusions. Usage is implied rather than directed.

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