Skip to main content
Glama

get_gas_benchmark

Read-only

Live gas price benchmarks for Ethereum, Base, and Solana. Returns Gwei, USD cost per transfer type, congestion category, and x402 agent economy context. Base vs ETH savings comparison. Source: public chain RPCs. Zero API key required. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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

Input Schema

NameRequiredDescriptionDefault
chainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses the paid x402 model ($0.10 USDC per call), the failure contract (HTTP 503 with no charge when upstreams are down), zero API key requirement, the upstream source (public chain RPCs), and a provenance field. That is unusually rich behavioral context for a read-only tool.

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?

Purpose is front-loaded and the operational details (pricing, error behavior) are compactly stated. The trailing 'data_source field discloses provenance (fred_api/fred_csv/fred_mixed)' is boilerplate that does not fit a gas-price tool and slightly dilutes the otherwise tight structure.

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?

With no output schema and one optional parameter, the description covers cost, failure mode, auth, data source, and return fields, which is close to complete. The remaining gaps are the omitted-default behavior for `chain` and the odd, unexplained FRED provenance reference.

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 coverage is 0% and the single `chain` parameter is never explained directly. The description does implicitly enumerate three of the four enum values (ethereum, base, solana), so the enumeration is partly recoverable, but 'all' and the default behavior when the parameter is omitted are left unstated.

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 first sentence names a specific resource and verb ('Live gas price benchmarks') and enumerates the covered chains (Ethereum, Base, Solana), which cleanly separates it from siblings like get_chain_tvl_benchmark or get_crypto_correlation_benchmark. The return fields are itemized, so an agent knows exactly what comes back.

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 by the domain and the mention of a 'Base vs ETH savings comparison', but there is no explicit when-to-use/when-not-to-use guidance and no naming of an alternative tool. An agent must infer the selection conditions from the purpose statement alone.

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