Skip to main content
Glama

SouthPow crypto & market data

buy_coin_HIGH

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

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

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 carries the full load and does well: it discloses that the call is paid, the exact price and payment rail (USDC on Base), that no account or API key is needed, and that failed calls are not charged. Missing only rate limits, latency/freshness, and error behavior.

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-loads the paid nature, then enumerates returned fields, then cost/requirements. Dense and waste-free, though the trailing raw URL and endpoint path add little for an agent that already has the tool bound.

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?

With no output schema, the description compensates by listing every returned metric and even naming the data sources (Coinbase Exchange with Kraken cross-check). Only data freshness/latency and the response envelope remain unspecified.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals a no-argument call by not inventing inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and verb-equivalent ('HIGH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'), pinning the exact symbol and dataset. Against hundreds of buy_coin_<SYMBOL> siblings, it makes clear this one returns HIGH/USD market data and nothing else.

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: the cost line ($0.25 USDC) and 'Failed calls not charged' let an agent judge whether the call is worth paying for, but there is no explicit statement of when to pick this over buy_crypto_price or a different symbol variant. No exclusions or prerequisites beyond 'no account, no API key' are given.

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