Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CATI

Paid. Catizen (CATI) 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/CATI.

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

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 behavioral burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted payment chains (Base or Solana), no account or API key requirement, and that failed calls are not charged. The only meaningful gap is that it says nothing about latency, rate limits, or freshness beyond 'live'.

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?

Every sentence earns its place: purpose first, then payload fields, then price/payment rails, then trust signals, then the endpoint. No padding or repetition, and the most decision-relevant facts (what it returns, what it costs) are front-loaded.

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 tool the description is nearly sufficient: the returned fields are enumerated and payment mechanics are fully spelled out. The one thing missing is disambiguation from the many sibling price tools covering the same or adjacent assets.

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 the baseline is 4. The description correctly does not invent parameter semantics, and the fixed CATI symbol is baked into the endpoint URL, which reinforces that no input is expected.

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 exact asset (Catizen, CATI) and the exact payload: live USD price, 24h change and market-cap rank. That is a concrete verb+resource. It stops short of differentiating itself from the near-identical sibling buy_coin_CATI, which an agent staring at both names would need.

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 only implied: 'if you want CATI price, call this.' There is no explicit when-to-use versus buy_coin_CATI, buy_crypto_price, or buy_tok_* alternatives, and no statement about when the tool would be the wrong choice. The purchase terms are clear, but routing guidance is absent.

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