Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GODS

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 that the call is paid ($0.25 USDC on Base), that no account or API key is required, that failed calls are not charged, and it names the upstream data sources (Coinbase Exchange with Kraken cross-check). It does not explain the payment mechanism (e.g. how the USDC is charged per request) or any rate limits.

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?

Dense and front-loaded: payment status first, then the data payload, then cost, auth, billing policy, and endpoint. The raw URL at the end is slightly awkward as prose but is informative rather than wasteful.

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 metrics and their sources. For a zero-parameter, single-endpoint data tool the definition is nearly sufficient; the only omissions are the payment flow and whether the response is JSON.

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. Baseline 4 applies; the description correctly avoids inventing parameter discussion.

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 specific resource (GODS/USD live price) and enumerates the exact fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. It implicitly resolves the ambiguity of the 'buy_coin_' prefix by showing this is a paid price-data fetch, not a coin purchase. It does not, however, distinguish itself from the generic sibling 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus buy_crypto_price or any other sibling. The presence of a generic price tool in the sibling list makes the missing routing guidance a real gap, since an agent cannot tell whether this symbol-specific endpoint is preferred over the general one.

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