Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CAT

Paid. Simon's Cat (CAT) 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/CAT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden, and it does disclose meaningful behavior: the call is paid, failure incurs no charge, and no credentials are needed. It stops short of explaining what a paid call actually returns structurally, whether data is cached or real-time, or any rate limits per payment — gaps that matter for an autonomous paying agent.

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-loads 'Paid' and the asset name, then the payload, then the price and rails, then the endpoint. Every clause carries operational information and there is no filler.

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?

With no output schema and no parameters, the description compensates by enumerating the three returned values and the payment mechanics, which is enough to decide whether to call it. A note on response format or data freshness would close the remaining gap.

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 nothing for the description to disambiguate; the baseline is a 4. The description correctly implies the asset is fixed at call time rather than passed as an argument.

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 (Simon's Cat / CAT) and the exact payload (live USD price, 24h change, market-cap rank), so the agent knows precisely what it is buying. It does not distinguish itself from the many similarly named siblings (e.g. buy_coin_* variants of the same asset class), leaving the token-vs-coin naming split unexplained.

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?

Practical invocation context is given: price of $0.05 USDC, payable on Base or Solana, no account and no API key required. However, there is no explicit when-to-use guidance nor any statement of when an alternative (e.g. a buy_coin_* tool) should be chosen instead.

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