Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NST

Paid. Ninja Squad Token (NST) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/NST.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 does add real value: it discloses the cost ($0.01 USDC), accepted payment rails (Base or Solana), that no account or API key is required, and that failed calls are not charged. Those are exactly the behavioral facts an agent needs before a paid call. It stops short of explaining rate limits, latency, or the actual payment handshake (e.g., how the USDC charge is settled), which is the riskiest unknown for an autonomous agent.

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?

Six short fragments, front-loaded with 'Paid.' so the agent sees the commercial constraint before anything else. Every clause carries distinct information — cost, data fields, payment rails, auth requirement, refund policy, endpoint — with no 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-argument, output-schema-less priced lookup, the description covers cost, auth, failure policy, payment networks, and the returned fields. The notable remaining gap is payment mechanics — how an agent actually authorizes or attaches the USDC payment on a call — which is central to correctly invoking a paid endpoint.

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 baseline is 4 and there is no parameter meaning for the description to compensate for. The description correctly does not invent arguments.

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 (Ninja Squad Token / NST) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is far more specific than the bare tool name. It does not, however, explain how it relates to near-duplicate siblings such as buy_crypto_price or the large buy_coin_* family, so an agent must infer which of many price tools is correct.

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 is implied rather than stated: an agent can infer this is the NST price lookup, but there is no explicit 'use this when...' or 'prefer X instead' guidance. Given hundreds of sibling price and token tools, a sentence distinguishing this endpoint from generic alternatives would materially change selection behavior.

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