Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FLUX

Paid. Flux (FLUX) 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/FLUX.

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

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 disclosure burden and does well: it states the cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no auth is required, and — importantly — that failed calls are not charged, plus the underlying endpoint. Gaps remain on rate limits, latency, and the exact response shape.

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?

Front-loads the payment flag and the payload description, then bulk-packs cost, chains, auth, and billing policy into short declarative fragments. The trailing URL is marginal for an agent selecting the tool but supports transparency; only minor compression loss from the telegraphic style.

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 per-asset price lookup with no output schema, the agent needs the data payload, cost, auth, and failure policy — all present. Return-value structure isn't detailed beyond the three named fields, but that is a small gap at this complexity level.

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 input schema is empty (0 params, 100% coverage), so the baseline is 4. There is nothing for the description to disambiguate, and it correctly introduces no parameter discussion.

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 exact asset (Flux/FLUX) and enumerates what the call returns — live USD price, 24h change, market-cap rank — so an agent can distinguish it from the hundreds of near-identical buy_tok_* and buy_coin_* siblings. It falls short of 5 because it never states the retrieval verb explicitly or contrasts itself with the generic multi-asset sibling buy_crypto_price.

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: if you need FLUX price data, call this. The description adds genuine prerequisites — paid, no account, no API key — but gives no when-to-use vs. when-not guidance and never points at an alternative (e.g. buy_crypto_price covering many assets or buy_coin_* family).

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