Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BEAM

Paid. BEAM/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/BEAM.

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

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, the description carries the full burden and does well: it discloses the $0.05 USDC-on-Base charge, that no account or API key is needed, that failed calls are not charged, and the upstream data sources plus the endpoint URL. Missing only rate limits, data freshness/latency, and response format, so it is strong but not exhaustive.

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?

It is a single dense block with no filler sentences, and cost/payment terms lead. The opener 'Paid.' is terse to the point of ambiguity and the sentence is run-on, which slightly hurts scanability, but nothing is wasted.

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 no-param, no-output-schema price endpoint, the description enumerates the returned fields, the payment terms, auth requirements, billing on failure, and data provenance — everything an agent needs before calling. Only the response encoding (JSON shape) and freshness are left unspecified.

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 nothing for the description to disambiguate; the baseline for a 0-param schema applies. The description correctly signals the coin is fixed by the tool name, requiring no symbol argument.

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 resource (BEAM/USD), the data returned (last price, 24h open/high/low, % change, 24h and 30d volume) and the sources (Coinbase Exchange with Kraken cross-check), so it is clearly distinguishable from the other buy_coin_* siblings. It never states an explicit verb, and the 'buy_coin_' name could mislead an agent into thinking a trade executes rather than a price lookup, which keeps it below 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer 'call this when you need BEAM spot/24h pricing'. There is no explicit when-to-use statement, no mention of when to prefer buy_crypto_price or another sibling, and no exclusions.

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