Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRABAI

Paid. Claude Crab (CRABAI) 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/CRABAI.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the $0.05 USDC cost, accepted payment chains (Base or Solana), absence of account/API-key requirements, and that failed calls are not charged. It still leaves out rate limits and exact payment mechanics, but the key operational traits 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 paid nature of the call, then the returned data, cost, access requirements, and endpoint URL. The fragmentary style is efficient, though 'Paid' and the explicit $0.05 charge are slightly redundant.

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 no-parameter paid price lookup with no output schema, the description is largely complete: it names the token, lists the three return fields, states the cost and payment chains, and explains access and failure charging. It could go further by specifying the exact response shape, but the essential calling context is covered.

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 has zero input parameters, so there are no parameter semantics to clarify. The description appropriately focuses on cost, access, and output data instead of inventing parameter guidance.

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 resource and token, CRABAI, and lists the returned data: live USD price, 24h change, and market-cap rank. It is specific enough to separate this from generic crypto-price tools, though it relies on the token ticker rather than an explicit statement of how it differs from other buy_tok_* siblings.

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 implied by the token-specific name and the stated price data, and the paid/no-account/no-API-key notes give important access context. However, it does not explicitly say when to choose this tool over alternatives such as buy_crypto_price or other token-specific feeds.

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