whale-insights

gas

Read-onlyIdempotent

Get real-time gas prices across 7 chains — ETH, SOL, BNB, Base, ARB, Polygon, AVAX with USD fee estimates — Current gas/transaction fees across ETH, SOL, BNB, Base, ARB, Polygon, and AVAX, with USD estimates per speed tier. 30s cache; check meta.cacheAgeSeconds for exact age. meta.chainCount tells how many networks are in the current response.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Response freshness metadata. 30s cache; check `meta.cacheAgeSeconds` for exact age.
`networks`	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"
+    },
+    "meta": {
+      "description": "Response freshness metadata. 30s cache; check `meta.cacheAgeSeconds` for exact age.",
+      "properties": {
+        "cacheAgeSeconds": {
+          "description": "Seconds since the cache was last refreshed.",
+          "type": "integer"
+        },
+        "chainCount": {
+          "description": "Number of chains/networks in this response.",
+          "type": "integer"
+        },
+        "updatedAt": {
+          "description": "ISO timestamp when this cache entry was populated.",
+          "format": "date-time",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "networks": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "level": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "standard": {
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJun 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavior beyond that: the 30-second cache, the meta.cacheAgeSeconds freshness check, and the meta.chainCount semantics. No contradiction with annotations.

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

Conciseness2/5

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

The chain list and 'USD estimates' are repeated almost verbatim: the first clause lists the 7 chains with USD fee estimates, and the following clause repeats the chains and USD estimates. This redundancy wastes a sentence, though the key cache and meta information is still front-loaded.

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?

For a parameterless, read-only tool with an output schema present, the description is complete: it lists the chains, explains freshness semantics, and documents the relevant meta fields. Nothing an agent needs to invoke this correctly 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?

The input schema has zero parameters, so the baseline for this dimension is 4. The description reinforces that no input is required by describing exactly what the response covers.

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 description uses a specific verb and resource ('Get real-time gas prices') and enumerates the seven supported chains, so an agent knows exactly what the tool returns. It does not contrast itself with the sibling gas_price_history, so it stops short of a 5.

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

Usage Guidelines4/5

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

The phrase 'real-time gas prices' plus the '30s cache' clearly establishes this tool as the current-state counterpart to historical tools. However, it never explicitly says 'use this instead of gas_price_history when you need current fees', so exclusion guidance is implicit rather than stated.

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?