Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FB

Paid. Fractal Bitcoin (FB) 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/FB.

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

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 at all, the description carries the full burden and does so well: it discloses the paid model and price ($0.05 USDC on Base or Solana), authentication-free access, and that failed calls are not charged. It omits rate limits and any latency or freshness caveats, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short front-loaded fragments: what it returns, what it costs, what access is required, what happens on failure. Nothing is repeated and the most decision-relevant facts come first.

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 price lookup with no output schema, an agent knows the payload fields, cost, payment chain, and failure billing. The only meaningful gap is the absence of any return-format or freshness indication, which matters slightly given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters and the schema is fully covered, so the baseline of 4 would normally apply. However, the description spends a sentence on an endpoint URL, which is not a parameter and adds no invocation meaning, so it is marginally less efficient than a clean zero-param definition.

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 asset (Fractal Bitcoin / FB) and the exact data returned: live USD price, 24h change, market-cap rank. That is far beyond a restatement of the name. It stops short of explicitly stating how it relates to the hundreds of sibling buy_tok_* tools, which is the only differentiation gap.

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?

It supplies the context that makes usage safe (no account, no API key, failed calls not charged) but never says when to choose this over alternatives such as buy_crypto_price or the other per-token tools. Guidance is implied by the asset symbol rather than stated.

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