Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GMT

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

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

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?

No annotations are supplied, so the description carries the full burden and does well: it discloses the $0.05 USDC-on-Base cost, that no account or API key is needed, that failed calls are not charged, and the underlying URL. It omits rate limits, latency, and what happens on partial data or upstream source disagreement.

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 description is compact and front-loads the 'Paid' flag and price fields before the cost and access terms. Every clause carries information; the only roughness is the terse telegraphic style and the URL tacked on at the end.

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 listing the returned fields (price, OHLC, % change, volumes) and naming the sources does the necessary work for an agent to know what it gets. The remaining gap is the response shape and units, which are only described in prose.

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 schema to document and the baseline is 4. The description correctly implies no inputs are needed, consistent with the empty schema.

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 exact resource and payload: GMT/USD live last price, 24h open/high/low, % change, and 24h/30d volume. It also clarifies that the call is a paid data purchase rather than an actual coin trade, which counters the misleading 'buy_coin_GMT' name. It does not explicitly contrast itself with buy_crypto_price or the other per-coin siblings, so sibling differentiation is only implied by the GMT scope.

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?

Usage is only implied: an agent can infer it should call this when it needs GMT/USD quotes from Coinbase with a Kraken cross-check. There is no statement of when not to use it, nor any pointer to buy_crypto_price as the general alternative. With hundreds of near-identical siblings, the definition leaves routing decisions to the agent.

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