Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GWEI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 it does well: it discloses that calls are paid, the exact price ($0.01 USDC on Base), the payment rail, that no account or API key is required, and that failed calls are not charged. The cross-venue sourcing (Coinbase Exchange with Kraken cross-check) also tells the agent how to interpret the numbers. It stops short of rate limits, latency, or response shape.

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?

Everything is front-loaded ('Paid.' then the data payload, then cost and prerequisites, then the URL), and every sentence carries information an agent needs before spending money. The clipped, footnote-like fragments are slightly harder to parse than prose but nothing is wasted.

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 is responsible for telling the agent what comes back, and it does by listing the returned fields and their sources. Combined with the cost and auth disclosures, this is nearly complete for a zero-parameter quote endpoint; only the output encoding and error behavior are left unstated.

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 and there is no parameter meaning for the description to add. The description correctly implies a parameterless call by identifying the asset in the tool identity itself rather than asking the agent to supply a symbol.

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 (GWEI/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume, plus the venues behind the numbers. That is far more specific than the bare tool name, which misleadingly suggests a purchase rather than a quote. It does not explicitly point to the sibling coin endpoints, so sibling differentiation rests on the symbol in the name.

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 only implied: an agent can infer this is the endpoint for GWEI price data. There is no statement of when to prefer this over buy_crypto_price or the other buy_coin_* tools, and no exclusion such as 'not for other assets'. The prerequisites that are stated (no account, no API key) are useful but are access conditions, not routing guidance.

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