Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ANA

Paid. Nirvana ANA (ANA) 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/ANA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does substantial work: it discloses that the call is paid, the exact price ($0.05 USDC), accepted chains (Base or Solana), that no credentials are required, and that failed calls are not charged. The main remaining gaps are rate limits, latency/freshness of the quoted price, and any retry or refund semantics beyond the failure case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It leads with 'Paid.' so the cost signal is front-loaded, then states the payload, then the commercial and technical terms in short declarative fragments. No sentence is redundant, and the trailing endpoint URL is useful rather than filler.

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-argument paid price lookup with no output schema, the description covers what an agent needs to decide and pay: data returned, cost, payment chains, credential-free access, and failure charging. Only operational details like rate limits and quote freshness are absent, which is a minor gap at this complexity.

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 per-parameter meaning to explain and the baseline is 4. The description correctly implies a parameterless call by embedding the asset in the URL rather than exposing a symbol argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific asset (Nirvana ANA) and the exact payload: live USD price, 24h change, and market-cap rank. That is a concrete verb-plus-resource statement an agent can match to a request without opening anything else, and the token-specific scoping distinguishes it from the generic price and TVL siblings.

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 rather than stated: an agent infers it should call this when it needs ANA spot price data. The description gives helpful preconditions (no account, no API key, cost, failure policy) but never states when to prefer this over sibling pricing endpoints such as buy_crypto_price or the buy_coin_* family, and gives no exclusions.

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