Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CHECK

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

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

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), that no account or API key is needed, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It stops short of describing freshness/latency or the response structure, which a zero-annotation paid tool ideally would.

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?

Front-loaded with 'Paid.' and then the payload, which is exactly the ordering an agent needs when cost matters. It is telegraphic in places and the raw endpoint URL adds little for invocation, but every other fragment earns its place.

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-parameter tool with no output schema, the definition covers cost, auth requirements, failure billing, data sources, and the fields returned. Missing only secondary details like response format and data staleness, which keep it from a 5.

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 clarify and the baseline is 4. The description correctly avoids inventing parameters such as a symbol or quote-currency argument.

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?

States a specific resource (CHECK/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. It is distinguishable from the hundreds of sibling buy_coin_<TICKER> tools by the ticker in the name/description, but it never explicitly says 'this is the CHECK variant; use another sibling for a different token'.

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: it is a live spot-price lookup for CHECK, and the 'Paid'/'$0.25 USDC' framing signals that a call costs money, which is a real usage consideration. There is no explicit when-to-use/when-not guidance, and no routing to alternatives such as buy_crypto_price or another coin's tool.

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