Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BUCK

Paid. Bucket Protocol BUCK Stablecoin (BUCK) 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/BUCK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only latency/rate-limit and response-format details for 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?

Roughly three short sentences: what it returns, what it costs and how to pay, then operational guarantees and the endpoint. Every clause is decision-relevant and the most important facts (asset, price) 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-argument, no-output-schema data fetch, the description covers payload, cost, payment rails, auth requirements, and failure billing. Only refresh cadence and response shape are unstated, which is a minor gap for a price snapshot 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 schema has zero parameters and no properties to document, which is the baseline-4 case. The description adds nothing to misunderstand and nothing to clarify, so the default applies.

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 exact asset (Bucket Protocol BUCK stablecoin) and enumerates the payload: live USD price, 24h change, market-cap rank. That is unambiguous about what a call returns. It loses the top mark only because it never positions itself against the generic sibling buy_crypto_price, which likely covers the same ground.

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 explicit statement of when to choose this over buy_crypto_price or any other price sibling, and no exclusions or prerequisites. The payment details imply a purchasing decision but do not tell the agent which tool to select for a BUCK quote versus a broader market call.

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