Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SHIB

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

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

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 price ($0.25 USDC on Base), the payment chain, that no account or API key is needed, that failed calls are not charged, and the underlying data sources (Coinbase Exchange with Kraken cross-check). What it omits is freshness/latency ('live' is undefined), rate limits, and whether the charge is incurred per call regardless of result quality.

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?

The most decision-critical fact ('Paid.') is front-loaded, and the field list follows immediately. Every clause carries information (cost, auth, refund policy, sources, endpoint). It is slightly dense — the parenthetical source note and the raw URL compete for attention — but nothing is padded.

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?

There is no output schema, so the description compensates by enumerating the returned fields, which is exactly what an agent needs to judge fit. Payment, authentication, and failure-charge behavior are all covered. The remaining gap is that the response shape (nesting, units, timestamps) and data freshness are 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 and the baseline of 4 applies. The description correctly implies a parameterless call by naming the ticker in the tool name and the URL path.

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 a specific resource (SHIB/USD) and enumerates exactly what it returns: last price, 24h open/high/low, % change, 24h and 30d volume. The sibling family (buy_coin_<TICKER>) is differentiated by the ticker embedded in the name, so an agent can tell SHIB apart from the other ~300 coin tools. However, it never explains how it relates to the generic buy_crypto_price sibling, and the name's 'buy_coin' prefix implies a purchase while the description describes a read-only price feed.

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 description implies usage by stating 'Paid' and 'No account, no API key', which tells the agent this is a callable data endpoint with no setup. But it gives no explicit when-to-use/when-not guidance and never contrasts itself with buy_crypto_price or any alternative source. The agent must infer selection purely from the ticker.

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