Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BOLD

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

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

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 behavioral burden well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. What it omits is response format and any rate/latency behavior, leaving a small gap.

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?

Front-loaded with 'Paid.' then the payload, then commercial terms, then the URL — every sentence carries distinct information. The raw URL is mildly operational rather than selection-relevant, which keeps it from a 5.

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 read with no output schema, the description names the returned fields (price, 24h change, cap rank) and the payment path, which is enough for correct invocation. It does not state the response shape or whether values are freshest at call time, a minor gap for a pricing tool.

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 schema cannot inform argument semantics and the baseline of 4 applies. The description correctly implies the token symbol is baked into the endpoint, leaving nothing for the caller to supply.

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 the specific resource (BOLD token) and the exact payload: live USD price, 24h change, market-cap rank. An agent knows precisely what it fetches. It does not disambiguate against near-siblings such as buy_coin_BOLD or buy_crypto_price, 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 statement of when to call this versus the many buy_coin_* / buy_crypto_price alternatives, and no exclusions. The only guidance is commercial (paid, no account), which helps with prerequisites but not with tool selection.

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