Skip to main content
Glama

SouthPow crypto & market data

buy_coin_G

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description supplies meaningful operational detail: a $0.01 USDC charge on Base, no account or API key, no charge for failed calls, and Coinbase/Kraken sourcing. It does not explicitly confirm that the operation is read-only and places no trade, nor explain payment handling or data freshness beyond 'live'.

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 its paid nature and exact data scope, followed by cost, access requirements, failure billing, and endpoint. Nearly every fragment adds actionable information, with only minor density from the telegraphic style.

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-argument tool without annotations or an output schema, it covers most selection and invocation needs: asset, metrics, sources, price, network, credentials, failure charging, and URL. It remains incomplete about response structure, precise freshness or calculation conventions, and the fact that no coin purchase occurs despite the tool name.

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 has no parameters, so there is no argument syntax to document. The fixed G/USD scope and endpoint URL make the zero-input behavior concrete and add useful invocation context.

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 fixed G/USD live market-data resource and enumerates last price, 24-hour open/high/low, percentage change, and volume metrics with named exchange sources. This distinguishes it from other asset-specific siblings, although it does not explicitly contrast the generic buy_crypto_price tool or state directly that it fetches a quote rather than buying G.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The fixed pair, live scope, and listed metrics make it clear that this is for current G/USD price and volume information. There are no explicit exclusions or routing guidance to buy_crypto_price for other assets, historical data, or different quote requirements.

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