Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GIGA

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

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

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, the description carries the full burden and does substantial work: per-call price of $0.002 USDC on Base, no authentication required, and the important guarantee that failed calls are not charged. It stops short of describing the response format, latency, or how payment settlement happens, which prevents a 5.

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 short and front-loaded, leading with 'Paid.' so the cost implication is visible before anything else, then listing the data payload and the commercial terms. The single dense stream of facts is readable but slightly cluttered by folding the raw URL into the same run-on sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must enumerate the returned fields, and it does exactly that. Combined with cost, auth, and failure-charging terms, an agent has everything needed to decide whether and how to call it.

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. The description correctly implies the ticker is fixed in the endpoint rather than supplied as an argument, which is the only parameter-relevant fact here.

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 concrete resource and exactly which fields come back: last price, 24h OHLC, % change, 24h/30d volume for GIGA/USD. That is specific enough to separate it from the ~700 coin siblings by ticker. It loses a point because the name says 'buy_coin' while the description describes a read-only price feed, leaving the agent to reconcile the naming.

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 implies usage through the 'Paid' framing and the stated prerequisites (no account, no API key, failed calls not charged), which helps the agent decide it can call this safely. However, it never states when to prefer this over the very similar siblings such as buy_crypto_price or the other buy_coin_* entries, nor any 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