Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DOOD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the cost ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the data provenance (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and response envelope shape, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly two sentences, front-loaded with the crucial 'Paid.' flag, then the payload, then cost/auth behavior. There is no filler; even the URL earns its place as an endpoint reference.

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 paid read with no output schema and no annotations, the description supplies the returned fields, the price, the auth model, and the failure-charging policy. It stops short of describing the response structure or units, which is the only real gap.

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 no parameter semantics to add; the baseline is 4. The description correctly implies the call is fully determined by the tool name and asks for nothing further from the caller.

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 specific resource (DOOD/USD live market data) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, with source venues. However, it never states a verb ('get'/'fetch') and only implicitly distinguishes itself from the other buy_coin_<TOKEN> siblings through the embedded ticker.

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 implied by the token-specific wrapping, but there is no explicit guidance on when to prefer this over buy_crypto_price or a sibling token endpoint, and no mention of the further reads (get_schema / search_facts) in the family. The payment and no-account notes give context for calling, not for choosing.

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