Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZANO

Paid. Zano (ZANO) 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/ZANO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 substantial work: it discloses that the call is paid, the exact price ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining payment mechanics (how the USDC charge is presented/authorized), latency, or how fresh the quoted price is.

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?

Front-loaded with 'Paid.' so the cost constraint is the first thing an agent sees, then the payload, then the price/rails, then the failure policy. Every clause carries distinct information and there is no filler or restatement of the tool name beyond the coin label.

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-param, annotation-free paid endpoint with no output schema, the description covers purpose, returned fields, cost, payment chains, and failure billing, which is close to what an agent needs before spending money. The remaining gap is the payment flow itself (how the $0.05 is settled, e.g. x402-style challenge) and the response shape, which has no schema to fall back on.

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 has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is argument-free and coin-scoped rather than suggesting any hidden options.

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 a specific verb+resource (live USD price, 24h change, market-cap rank for Zano) rather than restating the tool name, so an agent knows exactly what data comes back. It does not draw an explicit boundary against the nearest alternatives, notably buy_crypto_price or the buy_coin_* family, leaving that differentiation to the token name in the tool identifier.

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 context is implied by the payload description (call this when you need ZANO spot price, 24h change, or rank) and by the prerequisites 'No account, no API key'. However, there is no explicit when-to-use versus the generic buy_crypto_price tool, no exclusion conditions, and no statement about when a fresh call is warranted versus cached data.

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