Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BONE

Paid. Bone ShibaSwap (BONE) 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/BONE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 full burden and does well: it discloses that the call is paid, the exact price and accepted payment chains, that no auth is required, and that failed calls are not charged — a meaningful billing/refund policy. It stops short of rate limits, latency, or per-call vs per-period billing mechanics.

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?

Front-loads 'Paid.' before anything else, then gives the payload, price, access terms and URL in one dense paragraph with no filler. Every clause carries distinct information an agent needs before invoking a paid call.

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 paid lookup with no output schema, the description is nearly complete: it names the returned data (price, 24h change, market-cap rank) and all commercial terms. Only exact response field names/shape are omitted, which is minor given how simple the payload is.

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 schema semantics to add; the description appropriately spends its words on cost and access instead of inventing parameter detail. The endpoint URL is included, which is extra orientation rather than parameter guidance.

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 verb: BONE (Bone ShibaSwap) live USD price, 24h change and market-cap rank, with a named endpoint. An agent knows exactly what data it gets, but the description does not distinguish this from sibling families like buy_coin_BONE or buy_crypto_price, so the scope-versus-siblings signal is only carried by the tool name.

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 is implied (get the BONE price) and access conditions are spelled out ($0.05 USDC on Base or Solana, no account, no API key), but there is no explicit when-to-use/when-not guidance and no mention of the closely related buy_coin_BONE or buy_crypto_price alternatives.

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