Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BREV

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 on cost ($0.25 USDC on Base), auth (no account, no API key), and failure policy (failed calls not charged). It stops short on how payment is actually executed, whether the charge precedes data delivery, and any rate limits, leaving real gaps for a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loaded, opening with 'Paid' and then listing exactly what data comes back. The pricing/terms sentence in the middle is load-bearing for a metered call, though the raw endpoint URL reads as routing metadata rather than description.

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, no-annotation tool, it covers what matters: data fields returned, cross-checked sources, cost, auth-free access, failure billing, and the endpoint. Only the mechanics of paying and the response encoding are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-baseline is 4, but the description adds no parameter meaning whatsoever. It is adequate by default rather than by merit.

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 pair (BREV/USD) and enumerates the returned data: last price, 24h open/high/low, % change, and 24h/30d volume. Nothing else in the wording is ambiguous, though it never explicitly says to use the matching per-symbol sibling tool for other assets.

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 rather than stated: the leading 'Paid' and '$0.25 USDC on Base' tell an agent this is a metered call worth weighing before invoking. There is no explicit when-to-use/when-not guidance or reference to an alternative (e.g. buy_crypto_price or a different symbol's sibling).

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