Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NCX

Paid. NovaChargeX Coin (NCX) 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/NCX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations, the description carries the full behavioral burden and does most of it: it discloses that the call is paid, the exact cost ($0.05 USDC), the accepted payment networks (Base or Solana), that no auth is needed, and that failed calls are not charged. The one notable omission is the mechanics of the payment handshake itself (e.g. what happens on first call versus after payment), but the cost and failure policy — the highest-risk unknowns — are covered.

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?

It is a single packed run of fragments, but every element — cost, payment rails, no-auth, no-charge-on-failure, endpoint URL — is actionable and placed early. The telegraphic style is dense rather than padded; only the raw URL is arguably filler since the agent does not construct the request itself.

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 paid lookup with no output schema, the description covers the return contents (price, 24h change, market-cap rank), commercial terms, auth posture, and failure billing. What is left out is response format/freshness detail, which is acceptable given the simplicity, but the unresolved relationship to buy_coin_NCX leaves a real ambiguity an agent must resolve.

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 no parameters, so there is nothing to document and the baseline of 4 applies. The description correctly adds no parameter noise.

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 (NovaChargeX Coin / NCX) and specific payload fields (live USD price, 24h change, market-cap rank), so an agent knows exactly what data comes back. It is weaker on sibling differentiation: a buy_coin_NCX tool exists alongside buy_tok_NCX, and nothing explains which of the two to pick or how buy_tok_* differs from buy_coin_* or 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. The closest thing is the practical note that no account or API key is required, which tells the agent it can call it freely but not whether it should prefer buy_coin_NCX, buy_crypto_price, or another sibling for NCX pricing.

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