Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BOME

Paid. BOOK OF MEME (BOME) 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/BOME.

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

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, the description carries the full behavioral burden and does it well: it discloses that the call is paid ($0.05 USDC on Base or Solana), needs no account or API key, and that failed calls are not charged. That covers cost, auth, and failure billing. It does not describe response shape or latency, but the listed metrics partly cover the return content.

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 with 'Paid,' then the resource and metrics, then cost/auth/refund terms. Almost every clause earns its place. The bare URL at the end is arguably redundant but harmless.

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, fixed-symbol price lookup with no output schema and no annotations, the definition covers what matters: what data is returned (price, 24h change, market-cap rank), what it costs, payment chains, and that failures are free. The main gap is that the return format is not spelled out, and there is no routing guidance among the many sibling price tools.

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 parameter semantics to document. Baseline 4 applies; the description correctly implies the call needs no arguments because the symbol is fixed in the tool identity.

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 resource and metric set: 'BOOK OF MEME (BOME) price: live USD price, 24h change and market-cap rank.' That is unambiguous. It does not, however, differentiate this tool from sibling token-price tools such as buy_coin_BOME or buy_crypto_price, so an agent cannot tell from the text alone why it should pick this one.

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?

Usage is only implied by the metric names. There is no explicit statement of when to call this versus the many sibling price tools (buy_coin_BOME, buy_crypto_price, buy_tok_* for other symbols), and no mention of when not to use it.

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