Skip to main content
Glama

Stratalize Intelligence

Get Gas Benchmark

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

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, open-world behavior, so the description's job is to add what annotations cannot. It does add real operational detail: no API key, a $0.10 USDC x402 charge, and an HTTP 503 with no charge on upstream failure. However, it also introduces a confusing inconsistency — the source is stated as 'public chain RPCs' while the data_source field is described as returning fred_api/fred_csv/fred_mixed, which appears to be boilerplate from a different tool and undermines trust in the provenance claim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is correctly front-loaded in sentence one, and the return-field inventory is useful. But the trailing pipe-delimited block mixes payment SLA, error codes, and an apparently misplaced provenance field, adding length without proportionate value. Several clauses could be dropped or moved without loss.

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 single-optional-parameter read tool with no output schema, the description covers the return payload shape, pricing, and failure mode, which is about as complete as an agent needs to call it correctly. The remaining gap is the undocumented 'all' enum value and the unresolved source/provenance conflict.

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 0% for the single optional 'chain' enum parameter, so the description must carry the meaning. It implicitly enumerates three of the four enum values (ethereum, base, solana) by naming those chains, but never explains what 'all' does or whether it aggregates across chains. Partial compensation, not full.

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 first sentence names a specific resource and scope: live gas price benchmarks for Ethereum, Base, and Solana, with the returned metrics (Gwei, USD cost per transfer type, congestion category) spelled out. That is far more specific than the surrounding sibling benchmarks and lets an agent recognize this as the gas-price tool. It stops short of a 5 because it never contrasts itself with any sibling (e.g. chain_tvl or defi_yield) to confirm boundary cases.

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 explicit when-to-use or when-not-to-use guidance, and no help selecting among the chain enum values despite 'all' being an option. The phrase 'Base vs ETH savings comparison' hints at a use case but is framed as a return value, not as guidance for when to call this tool. The agent must infer the trigger condition entirely.

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