Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ETHW

Paid. EthereumPoW (ETHW) 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/ETHW.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 behavioral burden and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), no auth required, and that failed calls are not charged — the latter being a genuinely decision-relevant billing policy. It stops short of rate limits, delivery mechanism, or latency expectations.

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?

Six short fragments, front-loaded with the cost signal 'Paid.' and then the payload description. No filler; even the URL is a concrete verification affordance rather than 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-param paid endpoint with no annotations and no output schema, the description supplies the essentials: price, payment rails, auth requirements, failure billing, and the fields returned. It could be slightly more complete by describing the concrete shape of the response (units, timestamp, refresh cadence), which matters since no output schema exists.

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 description's implicit endorsement is that no symbol argument is needed because the token is baked into the endpoint.

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

Purpose5/5

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

States a specific resource (EthereumPoW / ETHW price) and exactly what is returned: live USD price, 24h change, market-cap rank. The per-symbol naming plus the explicit token identity makes it distinguishable from the hundreds of buy_tok_* siblings at a glance.

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?

The 'Paid.' prefix plus the price, payment chains, and 'no account, no API key' line make the commercial context clear, so an agent knows what it is committing to. However, it never says when to prefer this over related tools like buy_coin_ETHW or buy_crypto_price, nor when not to call it — the selection logic is left to the agent.

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