SouthPow API

buy_tok_BABYCLAW

Paid. Baby Claw (BABYCLAW) 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/BABYCLAW.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

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 burden and does well: it discloses the paid model ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged — meaningful cost/auth behavior an agent must know before calling. It omits rate limits and latency/refresh cadence for a 'live' price.

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?

A single tight line with the payload description front-loaded, followed by price/auth guarantees and the endpoint URL. Every clause carries information; the raw URL is marginally useful but not wasteful.

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?

A zero-parameter, no-output-schema tool is well served here: the returned fields are enumerated (USD price, 24h change, market-cap rank) and the cost/auth model is stated. Only the response shape/format and freshness semantics are left implicit, which is a minor 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; baseline applies. The description correctly implies no inputs are needed.

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?

States a specific resource and verb: BABYCLAW USD price with 24h change and market-cap rank. The token symbol is embedded in the tool name and repeated in the description, so it is distinguishable from the many sibling buy_tok_* tools. It stops short of stating explicitly that it is the BABYCLAW-specific endpoint versus the generic buy_crypto_price / buy_coin_* family.

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 resource (fetch this token's price) but there is no explicit when-to-use or when-not guidance relative to buy_crypto_price, buy_coin_BABY, or buy_tok_BABYDOGE/BABY. The payment logistics are given, but no alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SouthPow API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?