Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BCHEM

Paid. Bitchemical Token (BCHEM) 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/BCHEM.

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

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 full behavioral burden and does a solid job: it discloses that the call is paid ($0.05 USDC), names the accepted payment chains (Base or Solana), confirms no auth is needed, and states that failed calls are not charged. It omits rate limits, latency, and any note on data freshness, which keeps it from a 5.

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 'Paid.' so cost is seen first, then the payload, then payment mechanics. The trailing raw URL is the least useful element and is the only real filler, but it is brief.

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, single-value lookup with no output schema, the description covers everything an agent needs before calling: cost, payment rail, auth requirements, billing on failure, and the exact fields returned. Only freshness/rate-limit expectations are unaddressed.

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 no schema semantics to add and the baseline is 4. The description correctly implies the token is fixed in the endpoint rather than passed as an argument, which prevents an agent from looking for a symbol parameter.

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 specific resource (Bitchemical Token / BCHEM) and enumerates exactly what comes back: live USD price, 24h change, and market-cap rank. That is far more specific than the bare tool name. It stops short of distinguishing itself from near-identical siblings like buy_coin_BCHEM or buy_crypto_price, so a 4 rather than a 5.

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?

The description gives useful call preconditions (no account, no API key, paid, failed calls free) but never states when to pick this over the many sibling price tools such as buy_crypto_price or the buy_coin_* family. Usage is therefore implied by the token name rather than explicitly routed.

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