Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DOGE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it declares the call is paid at $0.10 USDC on Base, requires no account or API key, and that failed calls are not charged — critical cost and auth information an agent needs before invoking. It also discloses data provenance (Coinbase Exchange with a Kraken cross-check), which tells the agent how to weigh the values. It falls short of describing latency, refresh cadence, or what a successful payload looks like.

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.' so the cost constraint lands before anything else, then compresses returned fields, price, payment, auth, and provenance into a few short clauses. The telegraphic style is slightly clipped but every clause carries information; nothing is padding.

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 description covers what it returns, what it costs, what auth is needed, and failure billing — the essentials for a paid data call. Missing only operational details such as response shape, freshness/latency, and whether the payment is per-call or session-based.

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 and the baseline 4 applies. The description usefully implies the coin and quote currency are fixed by the endpoint rather than supplied as arguments.

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 (DOGE/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It never quite states a verb (fetch/return), and the tool name 'buy_coin_DOGE' suggests a purchase while the description describes a price-data call, so the agent must reconcile that itself. Still, the scope is unmistakable and clearly distinct from the HN, insider, and Polymarket siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no routing to alternatives. This matters because the sibling list contains buy_crypto_price, a generic price tool, yet the description never says whether to use this DOGE-specific endpoint instead of it or alongside it. Payment mechanics are disclosed, but selection criteria are absent.

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