Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JOHN

Paid. Little John (JOHN) 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/JOHN.

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

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 most of it well: it declares the tool is paid, the exact price and payment chains, that no account or API key is required, that failed calls are not charged, and the underlying endpoint URL. It stops short of describing rate limits, payment mechanics (e.g. x402 flow), or response shape beyond field names.

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 most decision-relevant fact ('Paid.') and then packs purpose, cost, auth, billing policy and endpoint into five short clauses with no filler. The raw URL and the slightly clipped phrasing make it read like a spec sheet rather than prose, but nothing is wasted.

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, single-datum paid endpoint with no output schema, an agent has everything needed to decide and invoke: what it returns, what it costs, where to pay, and that failures are free. Only the response encoding/format is left unspecified, a minor gap for 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 tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly avoids inventing arguments and instead pins the token identity into the tool name and prose.

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?

Names a concrete resource (Little John / JOHN) and the exact payload (live USD price, 24h change, market-cap rank), so an agent knows precisely what it returns. It does not explicitly distinguish itself from near-neighbours like buy_crypto_price or the buy_coin_* family, which is the only thing keeping it off a 5.

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 can infer 'call this when you need JOHN's price', and the '$0.05 USDC on Base or Solana' line sets the cost precondition. There is no explicit when-not or routing to the alternative price tools in the sibling list.

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