Skip to main content
Glama

SouthPow crypto & market data

buy_coin_B3

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 full burden and does well: it discloses the payment model, exact price, absence of auth requirements, the no-charge-on-failure policy, and the upstream data sources plus cross-check. It does not describe rate limits, latency, or error response shape.

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 four short clauses, each carrying distinct information: paid status, data content and sources, price/auth/failure terms, and endpoint URL. The leading 'Paid.' front-loads the cost caveat, and no sentence is 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-param, no-output-schema tool, the description adequately covers what data comes back, where it comes from, what it costs, and that failures are free. It could be slightly more complete by indicating the response format (e.g. JSON) or the failure/error behavior beyond billing.

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 beyond the implicit subject (B3/USD), which it does state explicitly. Baseline for a zero-parameter tool 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 states a specific resource and scope: B3/USD live price with an enumerated field list (last price, 24h open/high/low, % change, 24h/30d volume) and named sources (Coinbase Exchange, Kraken cross-check). Sibling differentiation is carried by the coin-specific tool name rather than the description text, so it falls just short of 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?

It tells the agent the call is paid, costs $0.25 USDC on Base, needs no account or API key, and that failed calls are free, which is useful preconditions context. It does not say when to prefer this over the generic sibling buy_crypto_price or how it relates to other coin tools, so usage is only implied by the coin-named tool.

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