Skip to main content
Glama

X420 agent services

x420_chain_gas-estimate

Read-onlyIdempotent

Base gas estimate: Current Base mainnet gas price, EIP-1559 fee estimate and base fee, reference costs for an ETH transfer and a typical ERC-20 transfer, and optionally an estimateGas for a call you describe (to, value, data). Source: Base mainnet RPC. L1 data fee not included. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.02 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: gas_price_gwei, max_fee_per_gas_gwei, base_fee_gwei, reference{eth_transfer, erc20_transfer_typical}, requested{estimate}.

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": "x420_chain_gas-estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNodestination address to estimate a call against (default: none)
dataNo0x calldata for the estimate (default: none)
fromNosender address for the estimate (default: none)
value_ethNoETH value for the estimate (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds crucial behavior they cannot convey: this hosted call does NOT return the deliverable, it only validates input and returns pay_to/network/price/x402 URL. It also states the price ($0.02 USDC) and a manual-versus-automatic payment route — genuinely useful context beyond annotations. Return format is fully listed, though nothing on latency or failure modes when the RPC is unreachable.

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?

Front-loaded with purpose before payment mechanics, which is the right order. Slightly verbose in the legal disclaimer boilerplate ('Not professional, legal, insurance, engineering, medical, financial or tax advice'), which is mandatory-ish but consumes attention without aiding invocation.

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?

With no output schema, the description carries the full return contract by naming every deliverable field, plus the payment handshake steps and the the L1 data fee exclusion. Nothing an agent needs in order to call it, or to understand what it gets back, is missing.

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?

Schema coverage is 100%, so the schema already documents all four parameters. The description nonetheless adds meaning by grouping to/value/data as the inputs that trigger the optional estimateGas call, which the schema does not convey, though it leaves out 'from' from that list.

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 verb+resource and enumerates exactly what is returned: gas_price_gwei, max_fee_per_gas_gwei, base_fee_gwei, reference costs, and an optional estimateGas. The scope line 'Source: Base mainnet RPC' plus 'L1 data fee not included' pins down exactly what is and is not measured.

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?

Gives strong operational guidance for the payment flow (GET the url, read PAYMENT-REQUIRED, retry with PAYMENT-SIGNATURE, or use the local x420-mcp server), but no guidance on when to choose this tool over alternatives such as wallet-balance or proof-of-payment. The optional estimateGas path is indicated only by the parenthetical '(to, value, data)'.

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