Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FXNW

Paid. FastX Network Token (FXNW) 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/FXNW.

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

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, the description carries the full burden and does well: it discloses the price ($0.01 USDC), accepted payment chains (Base or Solana), no account or API key needed, and that failed calls are not charged. What it omits is rate limits, latency, and what an error/refund actually looks like.

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 text is short, front-loaded with the return payload, then cost, then payment/auth terms. The telegraphic style ('$0.01 USDC on Base or Solana. No account, no API key.') is efficient, though the trailing bare URL is of marginal value to an agent that already invokes the tool by name.

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 paid lookup, the description covers the essentials: what is returned (USD price, 24h change, market-cap rank), what it costs, on which chains, and the failure-charging policy. Missing only peripheral details such as response shape or update freshness.

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; baseline 4 applies. The schema is empty and required=[], and the description correctly frames the call as parameterless by fixing the token (FXNW) in the tool itself.

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 states a specific verb and resource: 'FastX Network Token (FXNW) price: live USD price, 24h change and market-cap rank.' That is far more informative than the name alone. It does not, however, distinguish itself from the many sibling pricing tools (buy_coin_*, buy_crypto_price, buy_tok_*), so sibling selection still requires inference.

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 only implied: an agent gathers that this is for looking up FXNW's price. There is no explicit when-to-use, no exclusion of alternatives such as buy_coin_FXNW-style multi-asset price tools or buy_crypto_price, and no note on when a paid call is warranted. The 'Paid' prefix at least signals cost awareness.

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