Skip to main content
Glama

SouthPow crypto & market data

buy_coin_STABLE

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

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

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 paid nature, exact price and payment currency/chain, that no credentials are needed, and the failure/refund policy. It adds source attribution (Coinbase Exchange with Kraken cross-check), which is meaningful behavioral context. It omits rate limits, latency, and whether repeated calls are billed per call.

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 cost critical fact ('Paid.') is front-loaded in the very first word, followed by payload contents and then payment mechanics — a sound ordering for an agent. The telegraphic sentence fragments are dense but each carries information; the raw URL is arguably the least useful element but not 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 must stand in for return values, and it does by listing the exact fields returned. Combined with the payment terms and no-auth guarantee, an agent has enough to call it and interpret the result. The missing piece is the response shape/format and error modes beyond 'failed calls not charged'.

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 to disambiguate and baseline is 4. The description does not waste words inventing parameter semantics, and the embedded URL documents the fixed resource endpoint.

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 (STABLE/USD) and enumerates the returned data points: last price, 24h open/high/low, % change, 24h and 30d volume. It is distinguishable from the hundreds of siblings only by the ticker, but the 'Paid' prefix and the data-feed framing usefully clarify that, despite the 'buy_coin' name, this charges $0.05 for market data rather than executing a trade.

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?

Prerequisites are covered ('No account, no API key', $0.05 USDC on Base, failures not charged), which is real guidance for invoking it. However, it never states when to prefer this over the similar generic sibling buy_crypto_price, nor any exclusion such as 'use only if you need STABLE specifically' — the selection logic is left implicit.

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