Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SIGN

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full behavioral burden, and it does disclose cost, payment rail (USDC on Base), auth-free access, failure billing, and data provenance (Coinbase Exchange with Kraken cross-check). Gaps remain on rate limits, latency, caching, and what a paid response actually looks like. Solid but not complete for a zero-annotation tool.

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?

It is dense but front-loaded: 'Paid.' flags the cost model immediately, then the data payload, then price/auth/failure terms. The telegraphic style (fragments, 'URL …') is efficient, though the trailing raw URL and source parenthetical are somewhat incidental.

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 no-parameter, no-output-schema price fetch, the description covers what is returned, from which venues, at what cost, and with what failure policy. It lacks only response-shape details (currency units, JSON vs text) and rate limits, which are minor for a single-value lookup.

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 disambiguate; the baseline of 4 applies. The description still adds value by defining which market pair and data vintage the fixed-argument call returns.

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 (SIGN/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It is clearly distinguishable from the hundreds of sibling buy_coin_* tools by ticker. It lacks an explicit verb ('Get'/'Fetch'), but the noun-phrase form still communicates what the call yields.

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 conveys the conditions of use well: paid at $0.01 USDC on Base, no account or API key needed, failed calls not charged. What it does not do is route the agent among alternatives — it never mentions the related sibling buy_crypto_price or any general price tool, nor states when NOT to use this per-coin endpoint.

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