whale-insights

gas_price_history

Read-onlyIdempotent

Get daily gas price history — ETH/BNB/ARB/POLY/BASE fast gwei + SOL lamports over up to 90 days — Daily historical gas prices across 7 blockchain networks. One row per day: ETH fast gwei, ETH standard gwei, BNB fast gwei, ARB fast gwei, POLYGON fast gwei, BASE fast gwei, and SOL priority fee in lamports. Useful for tracking gas fee trends and identifying high/low gas periods. DB-backed, 5-min cache. Powered by gas_price_daily table (365d retention, permanent monthly archive). — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days of history to return (1–90, default 30).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`total`	No
`history`	No
`updatedAt`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "$ref": "#/components/schemas/Attribution"
+    },
+    "days": {
+      "type": "number"
+    },
+    "history": {
+      "items": {
+        "properties": {
+          "arbFastGwei": {
+            "description": "Arbitrum fast gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "baseFastGwei": {
+            "description": "Base (Coinbase L2) fast gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "bnbFastGwei": {
+            "description": "BNB Smart Chain fast gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "date": {
+            "description": "YYYY-MM-DD snapshot date.",
+            "format": "date",
+            "type": "string"
+          },
+          "ethFastGwei": {
+            "description": "ETH fast gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "ethStandardGwei": {
+            "description": "ETH standard (safe) gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "polyFastGwei": {
+            "description": "Polygon fast gas price in gwei.",
+            "nullable": true,
+            "type": "number"
+          },
+          "solLamports": {
+            "description": "Solana priority fee in lamports.",
+            "nullable": true,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: DB-backed, 5-min cache, 365-day retention, permanent monthly archive, and one-row-per-day format.

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 front-loaded with the core purpose and then expands into data details and usage guidance. It is somewhat dense with repeated mentions of 'gwei' and a long network list, but every sentence contributes value and the structure is logical.

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 an output schema present, annotations covering safety, and a single fully documented parameter, the description supplies all needed context: data scope, retention, freshness, and routing to sibling tools. An agent can correctly invoke this tool with no missing information.

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 documents the 'days' parameter with min, max, default, and a clear description, giving 100% schema coverage. The description mentions 'up to 90 days' but adds no new semantic meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Get daily gas price history' and enumerates the exact networks and metrics (ETH/BNB/ARB/POLY/BASE fast gwei, SOL lamports). It clearly differentiates from siblings by explicitly contrasting with the live snapshot tool and monthly tool.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.' This tells an agent exactly when to select this tool over alternatives.

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

All whale-insights tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?