Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BERA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description still discloses the behaviors that matter most for a paid call: a $0.10 USDC fee on Base, no account or API key requirement, and no charge for failed calls. Naming Coinbase Exchange and the Kraken cross-check also provides useful data-provenance context.

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?

The description is compact and front-loaded with 'Paid' and the BERA/USD data scope. Every fragment adds useful scope, provenance, cost, access, billing, or endpoint information without filler.

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-input paid quote tool without an output schema, listing the returned metrics, sources, fee, network, authentication needs, and failure billing covers nearly all invocation essentials. It could be more complete by clarifying selection versus buy_crypto_price and describing the response or payment mechanics.

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?

There are zero parameters, so no parameter documentation is required and the baseline is 4. The fixed BERA endpoint reinforces that the asset and pair are not configurable.

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 a live BERA/USD market-data lookup and enumerates the exact price, change, and volume fields, so the potentially misleading buy_coin name does not leave the operation ambiguous. It does not distinguish this asset-specific tool from buy_crypto_price.

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?

The asset, pair, and field list imply that it should be used when current BERA market data is needed. There is no explicit when-not guidance or direction to buy_crypto_price for other price-data needs.

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