Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NXPC

Paid. Nexpace (NXPC) 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/NXPC.

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

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 at all, the description carries the full burden and does comparatively well: it discloses the $0.05 USDC charge, both accepted payment chains (Base, Solana), that no account or API key is required, and that failed calls are not billed. It omits refresh cadence, latency, and what the failure modes look like, so it is not exhaustive.

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?

Six short fragments, cost and payload front-loaded, with no filler sentences. The trailing raw URL adds little for an agent that cannot call HTTP directly, but it is short enough that it does not meaningfully dilute the definition.

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, single-datum paid lookup with no output schema and no annotations, the description covers payload, price, payment rails, and billing behavior on failure. The remaining gap is that the shape of the returned fields (rank as integer? change as percent?) is left entirely to the response, which no structured field documents.

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 beyond confirming that the token is fixed in the endpoint itself. The URL makes clear NXPC is baked into the path rather than passed as an argument, which is the one useful semantic point available here.

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 specific asset (Nexpace/NXPC) and enumerates the exact data returned: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the many sibling buy_tok_* tools by ticker alone, though it never states how it differs from the generic buy_crypto_price sibling, which likely overlaps.

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?

"Paid" at the front signals a cost gate, and the price/rail line tells an agent what invocation costs, which is real usage context. However, there is no explicit guidance on when to choose this over buy_crypto_price or a buy_coin_* alternative, and no note on when a price lookup is or isn't warranted.

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