Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BC

Paid. BCGame Coin (BC) 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/BC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses cost, accepted payment rails, absence of auth requirements, and the failure-billing policy. It omits any statement about latency, caching/freshness of the 'live' price, or rate/usage limits, which would matter for an externally paid endpoint.

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 most important fact ('Paid.') and packs purpose, output fields, price, rails, auth, and billing policy into two terse sentences with no filler. The trailing raw URL is marginally useful but is the one element that could be cut without loss.

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 paid endpoint, the description supplies what the agent needs: what data comes back, what it costs, how to pay, and that failures are free. It does not describe the response shape or freshness guarantees, but with no output schema that is a minor rather than blocking 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 input schema has zero properties, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly implies the call is fully parameterized by the tool name (token fixed as BC, quote currency fixed as USD).

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 a specific verb and resource ('BCGame Coin (BC) price') and enumerates the exact outputs (live USD price, 24h change, market-cap rank). Since the token is fixed by the tool name, it is trivially distinguishable from the hundreds of sibling buy_tok_* tools covering other assets.

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

Usage Guidelines4/5

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

Gives clear selection context a caller needs: it is a paid call, costs $0.01 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. It does not state when a caller should prefer an alternative (e.g., a free aggregate price tool) or any exclusions, so it stops short of the 5 bar.

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