Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NXM

Paid. Nexus Mutual (NXM) 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/NXM.

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

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 a good job: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is needed, and that failed calls are not charged. It does not cover rate limits, caching/TTL for 'live' data, or latency, which keeps it from 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?

The payment model and the returned fields are front-loaded in two short clauses, then cost and access requirements, then the endpoint URL. Every sentence earns its place, though the telegraphic 'Paid.' fragment and bare currency list read more like marketing copy than a specification.

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 price endpoint, this is close to complete: the agent knows what data it receives, what it costs, which chains settle payment, and that failures are free. Missing only refresh cadence and whether the response is JSON-shaped, minor gaps for a tool this simple.

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 semantics to explain and the baseline is 4. The description correctly adds no irrelevant input chatter, since everything is fixed by the endpoint 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?

The description names a specific resource (Nexus Mutual / NXM) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. That is far more than a restatement of the name. It stops short of distinguishing itself from the large buy_coin_* / buy_crypto_price families, so an agent gets no explicit reason to pick this over a sibling.

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 by the resource name and the returned fields, and the payment mechanics ('$0.01 USDC on Base or Solana') help an agent decide whether it can afford the call. However, there is no explicit when-to-use statement and no named alternative for broader or non-NXM price queries, which matters given the hundreds of adjacent buy_tok_* tools.

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