Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NPC

Paid. Non-Playable Coin (NPC) 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/NPC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well on the commercially critical traits: it is a paid call ($0.05 USDC), payable on Base or Solana, requires no account or API key, and failed calls are not charged. It omits rate limits, latency, and payment-flow mechanics (how the USDC is actually remitted), so not a 5.

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?

Terse and front-loaded: payment status first, then payload, then price/rails, then auth and billing policy, then endpoint. Every clause adds information. The trailing raw URL is slightly redundant for a tool invocation but still useful as provenance.

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, no-output-schema tool, the description must itself convey return values, and it does so precisely (USD price, 24h change, market-cap rank) while also covering cost, chain, auth, and failure billing. Missing only response-shape detail such as field names or freshness/caching semantics.

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 no parameter meaning to add and the baseline is 4. The description correctly signals a no-argument call by embedding the token (NPC) in the fixed URL.

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 specific payload: 'Non-Playable Coin (NPC) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what it receives. It does not, however, distinguish this from the many sibling lookalikes (buy_coin_NPC, buy_crypto_price, buy_tok_* for other tokens), so the agent must infer the choice from the token symbol 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?

Use is only implied: 'price of NPC' plus a stated cost of $0.05 USDC. There is no explicit 'use this instead of buy_coin_NPC / buy_crypto_price' routing, nor any statement of when NPC pricing is or isn't the right fetch, leaving the agent to guess among near-identical siblings.

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