Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AMERICA

Paid. America Party (AMERICA) 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/AMERICA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 so well: it declares the call is paid, the exact price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of describing the payment handshake (e.g. how the USDC is presented) or whether the quoted price is real-time versus cached, but the cost and failure-charging disclosures are the operationally important ones.

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?

Content is front-loaded — 'Paid' first, then what you get, then cost and access terms — with no filler sentences. It is dense and telegraphic rather than verbose, though the trailing raw URL and the doubling of 'No account, no API key' are slightly redundant.

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 lookup, the description supplies the essentials an agent needs: what fields come back, that it costs money, how much, on which chains, and that failures are free. The one gap is the mechanics of actually settling the $0.01 payment, which an agent must know before the first call.

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 for the description to explain; the baseline for a no-arg tool applies. The description correctly adds no spurious argument talk and instead spends its words on the response contents and payment model.

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 specific resource (America Party / AMERICA token) and exactly what is returned: live USD price, 24h change and market-cap rank. That is a clear verb+resource statement, but it never explains how this differs from the many parallel look-alikes such as buy_coin_AMERICA-style siblings or 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The only quasi-guidance is the 'Paid' prefix and access conditions, which describe cost rather than selection criteria. In a catalogue of hundreds of near-identical buy_tok_* tools, an agent is left to infer the choice entirely from the tool name.

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