Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANTFUN

Paid. AntFun (ANTFUN) 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/ANTFUN.

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

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: it discloses cost ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of explaining how payment is actually settled (e.g., x402 handshake) or whether repeated calls within a window are billed separately.

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, front-loaded with the paid warning and followed by payload, price, access terms, and endpoint. Every clause is informative; the raw URL is the only element of dubious value to an agent that does not construct HTTP calls itself.

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 adequately covers what is returned and what it costs. The remaining gap is payment mechanics: an agent knows the price but not the exact protocol step needed to actually complete the $0.05 settlement.

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; the baseline applies. The description correctly implies no arguments are required and no identifier needs to be supplied, since the asset is baked into the tool.

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 resource (AntFun/ANTFUN price) and the exact payload (live USD price, 24h change, market-cap rank), so the agent knows precisely what comes back. It does not, however, differentiate itself from the many sibling buy_tok_* / buy_coin_* / buy_crypto_price variants, so an agent scanning siblings gets no explicit routing rule.

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: call this when you need ANTFUN's spot price, change, and rank. There is no explicit when-not guidance and no reference to an alternative generic price tool, which matters in a catalog with hundreds of near-identical paid price endpoints.

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