MCP Etherscan Server

get-gas-prices

Retrieve current Ethereum gas prices in Gwei for any supported network. Specify network name or chain ID to get real-time gas estimates.

Instructions

Get current gas prices in 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": "get-gas-prices"
  }
}

Input Schema

Name	Required	Description	Default
`network`	No	Network name or chain ID (default: ethereum mainnet)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Mar 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get current gas prices in Gwei', but does not disclose how the data is fetched, whether it is cached, rate limits, or error handling. The behavioral transparency is minimal.

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 description is a single concise sentence that earns its place by stating the purpose. However, it could include more detail without losing conciseness, such as mentioning the possible return format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should hint at the return value (e.g., whether it returns a single number or an object with slow/average/fast prices). It lacks this context, making it incomplete for an agent to understand the output.

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?

The input schema already fully describes the single parameter ('network' with default). The description adds no additional meaning about the parameter beyond what the schema provides. With 100% coverage, baseline is 3.

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 clearly states that the tool retrieves current gas prices in Gwei, using a specific verb and resource. It distinguishes itself from sibling tools like 'check-balance' or 'get-network-stats' by focusing on gas prices.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, such as 'get-network-stats' which might include gas prices. No prerequisites or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.