Skip to main content
Glama

SouthPow crypto & market data

buy_coin_COOKIE

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

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

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 substantial work: it discloses the cost ($0.25 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the underlying data sources. It stops short of stating rate limits, latency, or whether the response is JSON, but the paid-call economics are clearly surfaced.

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 a dense telegraphic block with no filler: cost first, then payload, then sources, then payment mechanics, then endpoint. The sentence-fragment style is efficient and front-loads 'Paid.', which is the most decision-relevant fact. Minor loss of readability from the fragments.

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?

There is no output schema and no annotations, so the description must describe both the return payload and the call mechanics, and it does: it lists the metrics returned and states the payment model. Only the response encoding/schema shape is left unstated, which is a modest gap for a zero-parameter call.

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 embedded URL does at least confirm the symbol is baked into the endpoint rather than passed as an 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?

The description names the exact resource (COOKIE/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, and 24h/30d volume. It also names the data provenance (Coinbase Exchange with a Kraken cross-check), which is unusually specific. It does not explicitly contrast itself with the mass of sibling buy_coin_* tools, though the ticker in the name does the differentiation.

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 context is implied: this is the paid single-asset spot for COOKIE price data. The description never says when to prefer it over the generic buy_crypto_price sibling, nor when not to call it. The 'Paid.' prefix and pricing line give the agent a cost signal but not a selection rule.

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