Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ZCAT

Paid. Anonymous Cat (ZCAT) 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/ZCAT.

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

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, the description carries the full behavioral burden and does most of it: it declares the tool is paid, the exact cost ($0.01 USDC), the two accepted payment chains, that no auth is required, and that failed calls are not charged. That billing-on-failure disclosure is the kind of detail annotations would otherwise never supply. It omits rate limits and whether the price is cached or real-time beyond the word 'live'.

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-loaded with 'Paid' and the price, then the data fields, then the payment mechanics - a sensible priority order for an agent deciding whether to call it. The style is telegraphic fragments rather than prose, which suits the content. The raw endpoint URL is the one element that is arguably noise for a caller that never supplies a URL.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, single-value price fetch with no output schema, the description covers everything an agent needs before calling: what data it returns, that it costs money, how to pay, that no credentials are needed, and that failures are free. Nothing material is left to inference given the tool's low 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 schema has zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly avoids inventing inputs (no asset symbol or chain argument) and instead spends its words on what is returned and what it costs.

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?

A specific verb-plus-resource statement: it fetches the live USD price for Anonymous Cat (ZCAT) along with 24h change and market-cap rank. The tool name already encodes the asset, and the description confirms which data fields come back, so an agent can distinguish it from the generic buy_crypto_price sibling. It stops short of naming that sibling explicitly, which keeps it from 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 context is implied rather than argued: it is a paid, single-asset price lookup, so the agent can infer 'use for ZCAT quotes'. Payment rails (Base or Solana) and 'no account, no API key' give practical prerequisites. There is no explicit statement of when to prefer this over buy_crypto_price or the buy_coin_* family, and 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