Skip to main content
Glama

SouthPow crypto & market data

buy_tok_XCAT

Paid. PUMPSTOP (XCAT) 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/XCAT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 well: it discloses that the call is paid, the exact cost and payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It does not describe rate limits or the response envelope, but the important operational constraints are present.

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?

The description is compact and front-loads the asset and returned data before payment details. The opening 'Paid.' is slightly redundant with the explicit pricing sentence, but the rest is efficient and every phrase carries useful information.

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 price lookup, the description provides enough context to call the tool correctly: it names the asset, lists the returned data fields, and explains payment requirements. It could mention the response format or data freshness guarantees, but overall it is complete 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, so there is no parameter semantics to explain. The description correctly avoids inventing parameters and focuses on the asset and payment flow, matching the baseline for a no-parameter tool.

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 clearly identifies the asset (PUMPSTOP/XCAT) and the data returned: live USD price, 24h change, and market-cap rank. It is specific enough to distinguish this from unrelated tools, but it does not explain why an agent should choose it over sibling price tools such as buy_crypto_price or buy_coin_* tokens.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this tool is for XCAT pricing. There is no explicit guidance on when to use it versus generic crypto-price tools or the many sibling coin tools, and no exclusions or prerequisites beyond payment details.

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