Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BMX

Paid. BitMart (BMX) 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/BMX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It does not specify latency, rate limits, or response shape, which keeps it out of 5 territory.

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?

Seven short clauses, front-loaded with 'Paid.' followed by the payload, then pricing, then access terms. Telegraphic but every sentence carries operational information; a slightly more explicit opening verb would improve readability.

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 definition covers what is returned, what it costs, how to pay, what credentials are avoided, and failure billing. Remaining gaps (freshness/latency, response structure beyond field names) are minor for this complexity.

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 baseline is 4; the description appropriately spends no words on parameter meaning and instead uses the space for cost and data-content context.

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 verb-implied resource and payload: 'BitMart (BMX) price: live USD price, 24h change and market-cap rank.' An agent knows exactly what data comes back. It does not differentiate from the very similar siblings buy_coin_BMX, buy_crypto_price, or buy_tok_* generic token tools, so it stops short of 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative. The description explains payment terms but never tells the agent why to pick this BMX feed over buy_coin_BMX or buy_crypto_price in a catalog of hundreds of near-identical paid tools.

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