Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ETH

Paid. ETH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ETH.

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

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 burden and does a good job: it discloses that the call is paid ($0.05 USDC on Base), that no account or API key is needed, that failed calls are not charged, and which exchanges supply the data. It stops short of rate limits, latency, or whether quotes are real-time versus delayed.

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?

Every clause earns its place: cost and auth constraints are front-loaded ('Paid.'), then the payload, then the data sources, then billing behavior and URL. No filler or restatement of the tool name.

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, so the description must carry return values — and it enumerates the fields returned, which is the key gap it needs to fill. It does not describe the response shape (JSON structure, units, timestamp field), which is the remaining shortfall for a paid data tool.

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 the baseline is 4; there is nothing for the description to disambiguate. The embedded endpoint URL is a minor plus, confirming the call needs no inputs.

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?

The description names the exact resource (ETH/USD live price) and enumerates the payload: last price, 24h open/high/low, % change, 24h and 30d volume, plus the two venues used. Against a sibling list of hundreds of buy_coin_<TICKER> tools, the ETH scope is unambiguous and the agent can tell this apart from buy_coin_BTC or buy_crypto_price immediately.

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 rather than stated: an agent infers 'call this when you need spot ETH/USD data.' There is no explicit when-not guidance and no routing to buy_crypto_price (the generic sibling) or to any other price source, so the agent must guess at the boundary.

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