Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PROMPT

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

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

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 at all, the description carries the full burden and does most of it: cost ($0.05 USDC on Base), no-auth operation, the crucial guarantee that failed calls are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and what happens on partial 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?

Extremely dense and front-loaded: cost, data fields, sourcing, payment terms, and endpoint in a handful of tokens. The telegraphic fragments ("Paid.", bare URL at the end) are slightly cryptic but nothing is wasted.

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 paid, parameterless, output-schema-less endpoint, the description covers payment, auth, failure billing, and the returned fields. What is missing is any indication of response format/structure (JSON shape) or error semantics, which matters since no output schema is supplied.

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 the baseline applies. The description correctly implies no arguments are needed to obtain PROMPT pricing.

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 (PROMPT/USD live price) and enumerates the returned fields — last price, 24h open/high/low, % change, 24h and 30d volume — which clearly separates it from the ~400 sibling buy_coin_* entries that cover other assets. It stops short of a clean verb-first statement (it opens with the terse fragment "Paid."), so an agent must infer that it retrieves data rather than trades it.

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?

It gives useful pre-call context (requires payment, no account/API key needed) that implies when the tool is usable. However, it never says when to prefer this over the sibling buy_crypto_price or a generic price tool, nor does it state any exclusion or freshness caveat.

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