Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BABYDOGE

Paid. Baby Doge Coin (BABYDOGE) 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/BABYDOGE.

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

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 provided, the description carries the full disclosure burden and does well: it names the cost and currency, the two accepted payment chains, the absence of authentication, the fact that failed calls are not billed, and a concrete endpoint URL. It omits rate limits, latency, and whether the charge applies per attempt, but the payment and failure semantics are exactly the kind of behavior an agent needs before invoking a paid tool.

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 text is short and front-loaded, leading with payment status and the exact fields returned before the cost, terms, and URL. Each sentence carries distinct information, though the telegraphic fragments ('Paid.' and the bare 'URL ...' clause) read as note-like rather than fully structured prose.

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 paid price lookup with no output schema, the description supplies enough: the exact data fields returned, the price, the payment networks, the no-auth requirement, and failure billing policy. It stops short of describing the response shape or data freshness, but an agent can call it correctly from what is given.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly signals a parameterless, single-token call rather than implying any filtering or configuration options.

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 uses a concrete verb and resource: it returns Baby Doge Coin (BABYDOGE) live USD price, 24h change, and market-cap rank. The token name is embedded in the tool name and restated, so an agent can distinguish it from the hundreds of sibling buy_tok_* tools. It does not explicitly distinguish itself from the broader buy_crypto_price sibling, which is the only minor ambiguity.

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?

It establishes the prerequisites for use (paid, $0.01 USDC on Base or Solana, no account or API key required) and notes that failed calls are not charged, which is useful retry context. However, it never states when to prefer this over buy_crypto_price or other price tools, nor any exclusions or freshness caveats, so usage guidance remains implied rather than explicit.

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