Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HONEY

Paid. HONEY/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/HONEY.

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

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 supplied, the description carries the behavioral burden and does well by disclosing that the tool is paid, costs $0.05 USDC on Base, requires no account/API key, and does not charge failed calls. It also gives the endpoint and names Coinbase Exchange with a Kraken cross-check, but it omits rate limits, how payment is attached to a successful call, and the response format.

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?

The description is compact and front-loads cost with 'Paid.' before listing the data fields, payment terms, and URL. The telegraphic fragments are efficient, though the jump from 'Paid.' to the data list is slightly abrupt.

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, no-output-schema price lookup, the description is nearly complete: it lists the returned metrics, sources, cost, auth requirements, failure charging policy, and endpoint URL. The remaining gap is that it does not explain the response format or payment mechanics, but those are minor for this simple 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 baseline is 4 and there is no parameter semantics gap for the description to fill. The description adds no parameter-specific meaning because none exist.

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 identifies the specific asset pair (HONEY/USD) and enumerates the exact market data returned: last price, 24h OHLC, percent change, and 24h/30d volume. It is distinguishable from sibling buy_coin_* tools by the HONEY symbol in both the name and description, though it does not explicitly state the action verb or contrast itself with the generic buy_crypto_price sibling.

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 by 'HONEY/USD live' and the HONEY-specific name, but there is no explicit when-to-use/when-not guidance or routing versus buy_crypto_price or the many other buy_coin_* tools. The description does supply useful prerequisites by saying no account or API key is needed and that failed calls are not charged.

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