Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BFG

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

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

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 provided, the description carries the full burden and does well: it discloses the paid model, the exact price and accepted chains, that no authentication is required, and that failed calls are not charged — all behavior an agent could not infer elsewhere. It omits response latency/freshness guarantees and how the paid call is settled at invocation time.

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 definition is short, front-loads the most decisive fact ('Paid.'), and every clause adds information (fields returned, price, chains, no auth, refund policy, URL). The telegraphic fragment style is efficient but borders on terse, with no explicit statement of what an agent gets back in terms of shape.

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 endpoint, the description covers purpose, cost, access, and failure policy — the things an agent must know before spending money. Only a brief note on response format or data freshness is missing, which is a minor gap given the absence of an output schema.

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 and an empty schema, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies a fixed, single-asset query with no filtering options.

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 (BFG Token price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. That is enough for an agent to know exactly what this endpoint yields. It stops short of differentiating itself from the large family of sibling price tools (buy_coin_*, buy_crypto_price), which it leaves to the naming convention.

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?

Usage context is implied: call this when you need BFG's price. The description adds payment and access conditions ($0.01 USDC on Base or Solana, no account or API key) but never states when to prefer this over the sibling buy_coin_/buy_crypto_price endpoints or any exclusions.

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