Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DHC

Paid. Doge Head Coin (DHC) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/DHC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 well: it discloses the paid cost ($0.01 USDC), accepted chains, that no account or API key is required, and the billing policy that failed calls are not charged. The gaps are return latency, caching/freshness of the 'live' price, and response shape, none of which are covered by an output schema.

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?

Five short clauses, each carrying distinct information: paid status, payload, price and rails, onboarding friction, failure billing, and endpoint. The essential purpose is front-loaded and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter paid lookup with no output schema, the description covers everything an agent needs: what it returns (three named fields), that it costs money, on which chains, that no auth is needed, and that failures are free. Return values are effectively enumerated in prose, substituting for the missing output schema.

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 input schema has zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It partially compensates by fixing the asset (DHC) and the endpoint URL in the text, so the caller knows no arguments are needed.

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 (Doge Head Coin / DHC) and the exact payload: live USD price, 24h change, and market-cap rank. It is immediately distinguishable from the hundreds of sibling buy_tok_* and buy_coin_* entries by naming DHC explicitly, though it never states why a caller would pick this over buy_crypto_price or buy_coin_* for the same asset.

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 'Paid' framing and the enumerated deliverables, and the payment path (USDC on Base or Solana) tells the caller the prerequisite. However, there is no explicit when-to-use guidance, no mention of the sibling tools covering the same asset, and no note on what happens if the token symbol is unsupported.

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