Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BFC

Paid. Bifrost (BFC) 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/BFC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does a reasonably good job: it discloses the price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. It omits data freshness/latency and response format, which matter for a live price feed.

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?

Roughly 40 words, front-loaded with cost status and the resource, then payment mechanics. Every sentence earns its place; only the terse 'Paid.' fragment and a bare URL keep it from being maximally clean.

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 tool with no output schema, the description usefully enumerates the returned fields and covers cost, auth and failure charging. The remaining gaps (freshness, response shape) are modest for a simple price lookup.

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 and there is no parameter meaning to add. The description correctly avoids inventing or implying any arguments.

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 states a specific resource ('Bifrost (BFC) price') and the exact fields returned: live USD price, 24h change and market-cap rank. That is far beyond restating the name. It does not, however, distinguish itself from the closely named sibling buy_coin_BFC or buy_crypto_price, so an agent cannot tell from the description alone which of the BFC-pricing tools to pick.

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, despite an entire family of sibling price tools (buy_coin_BFC, buy_crypto_price). The payment and no-account details enable the call but do not help route between candidates.

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