Skip to main content
Glama

Chain gas price (x402)

chain_gas_price

Read-onlyIdempotent

$0.002 via x402: live network gas prices (slow/average/fast, in gwei) for any chain — the pre-transaction read every trading, sniping and settlement agent makes before sending a tx to size the fee. Across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. Live from Blockscout; one paid call instead of running your own RPC.

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": "chain_gas_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase|ethereum|optimism|arbitrum|polygon|gnosis (default ethereum)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, and openWorld, and the description adds substantive context beyond them: a concrete price point ($0.002), the x402 payment requirement, and the upstream source (Blockscout). The payment prerequisite is the operationally critical disclosure here and it is stated plainly, though the description doesn't say what happens if the payment payload is invalid or expired.

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?

The core capability is front-loaded in the first clause, followed by the use case and the differentiator. It is dense but not padded, though the marketing cadence ("every trading, sniping and settlement agent") is longer than strictly needed.

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 two-parameter, zero-required tool with no output schema, the definition covers cost, source, supported chains, return granularity (slow/average/fast in gwei), and the payment step. No significant gap remains for correct invocation, though the paid flow's failure behavior is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both the chain values and the x_payment/base64 semantics documented in the schema itself. The description repeats the chain coverage list and adds no format or default detail the schema lacks, so it earns the baseline rather than more.

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 states a specific verb and resource — "live network gas prices (slow/average/fast, in gwei)" — and scopes it to "any chain" with a named supported list. It is clearly distinguishable from siblings like chain_transaction_explain or pretrade_full_report, which do not return raw gas tiers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit timing context — "the pre-transaction read every trading, sniping and settlement agent makes before sending a tx to size the fee" — and positions the alternative as "one paid call instead of running your own RPC." It does not name a specific sibling tool to use instead for any overlapping case, so it stops short of full 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