Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BITCOIN

Paid. HarryPotterObamaSonic10Inu (ETH) (BITCOIN) 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/BITCOIN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does well: it discloses that calls are paid ($0.01 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged — all non-obvious facts an agent must know before calling. It stops short of any hint about rate limits, timeouts, or what an error response looks like.

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?

Front-loads the critical word 'Paid.' and the concrete return values, then payment terms, then a raw endpoint URL. The fragments are telegraphic but each carries distinct information; the bare URL at the end is the only arguably expendable element.

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 tool this is nearly complete: the agent knows what comes back, what it costs, how to pay, and that failures are free. The only gap is the absence of any statement about response format or freshness/latency, which matters slightly for a 'live' price feed.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly avoids inventing parameters and instead pins down the asset identity, which is the only 'input' the agent controls by tool choice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the exact resource (the BITCOIN-tickered HarryPotterObamaSonic10Inu/ETH token) and the exact payload: live USD price, 24h change, market-cap rank. Crucially it disambiguates the ticker from real Bitcoin, which the tool name buy_tok_BITCOIN alone would not do, and separates it from the ~600 buy_tok_* siblings by naming the token.

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 makes clear this is a paid price lookup for one specific token, which implies the use case, but it never names an alternative (e.g. buy_crypto_price or buy_coin_BTC) or states when an agent should prefer a different tool. The agent has to infer the selection rule from the huge sibling list on its own.

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