Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NKYC

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

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

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 present, the description carries the full burden and does a solid job: it discloses the pay-per-call cost, accepted payment chains, the absence of auth requirements, and the favorable billing rule that failures are not charged. What it omits is response behavior — freshness/caching, latency, and error shape — plus the mechanics of how payment is actually attached to the request.

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?

Seven short fragments, front-loaded with the paywall flag and the core payload, then cost, then auth, then billing, then endpoint. The only redundancy is 'NKYC Token (NKYC)', which is trivial and arguably disambiguating. Nothing else could be cut without losing a fact an agent needs.

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 endpoint with no output schema, the description covers the gaps that matter: what fields come back, what it costs, how to pay, and that failures are free. The endpoint URL is a useful addition. It falls one step short of complete because the payment mechanism (how the USDC is presented to the server) is not described.

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 and the baseline applies. The token identity is baked into the tool name, which the description reinforces, so an agent cannot mis-supply an argument.

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 the exact resource (NKYC token) and enumerates the returned data: live USD price, 24h change, market-cap rank. That is a specific, checkable purpose rather than a restatement of the name. It stops short of distinguishing itself from the ~1000 sibling buy_tok_* tools by rule (e.g., 'one tool per symbol'), so an agent must infer the per-token pattern from the name alone.

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 real operational context — paid at $0.05 USDC on Base or Solana, no account or API key, failed calls not charged — which tells the agent the cost and prerequisites of invoking it. It gives no when-to-use routing, though: nothing says whether to prefer buy_crypto_price or buy_coin_NKYC for the same asset, or how to reach another token's price. Usage is implied by the name, not stated.

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