Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DOGINME

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

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

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, the description carries the full burden and does a decent job: it discloses that the call is paid ($0.25 USDC on Base), that no account or API key is required, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency, and response format, but the payment/auth/failure profile — the highest-risk behaviors for an agent — is covered explicitly.

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?

Dense and front-loaded: payment model first, then returned fields, then cost/auth/billing terms, then endpoint. No filler, though the telegraphic fragments ('Paid.', 'URL https://...') read as machine-compressed rather than prose, and the endpoint URL arguably belongs in structured metadata rather than the description.

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 fetch tool, the description supplies the returned field list, the data sources, the price, the auth requirement, and the billing-on-failure rule — everything an agent needs to invoke it and interpret the result. The main residual gap is the unexplained 'buy' framing, which is a naming problem the description does not compensate for.

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 for the description to add; the schema is empty and 100% covered. Baseline for a 0-parameter tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what is returned (last price, 24h open/high/low, % change, 24h and 30d volume for DOGINME/USD) and names the data sources, which is genuinely specific. But it never states a verb and never resolves the mismatch between the tool name ('buy_coin_...') and the fact that this is a read-only price feed — an agent could read 'buy_coin' as executing a purchase. Purpose is identifiable but the framing is left implicit.

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?

No explicit when-to-use or when-not-to-use statement, and no reference to alternatives such as buy_crypto_price or sibling per-coin tools. The cost/auth/failure-billing facts ('$0.25 USDC on Base. No account, no API key. Failed calls not charged.') do give an agent the information needed to decide whether paying for this call is worthwhile, so usage is implied rather than 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