NatGasLens — US Natural Gas & Henry Hub Data

get_us_natural_gas_production_nowcast

Read-onlyIdempotent

Daily/monthly US dry natural gas production nowcast (Bcf/d), estimated from the year-ago level scaled by a YoY growth trend and anchored to news, with a per-month series (est vs EIA actual once published). Demo scope hides the freshest month's estimate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`asof`	No
`data`	No
`note`	No
`tool`	No
`scope`	No
`stale`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "asof": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Asof"
+    },
+    "data": {
+      "additionalProperties": true,
+      "default": null,
+      "title": "Data",
+      "type": "object"
+    },
+    "disclaimer": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Disclaimer"
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Note"
+    },
+    "scope": {
+      "default": null,
+      "title": "Scope",
+      "type": "string"
+    },
+    "stale": {
+      "default": null,
+      "title": "Stale",
+      "type": "boolean"
+    },
+    "tool": {
+      "default": null,
+      "title": "Tool",
+      "type": "string"
+    }
+  },
+  "title": "Envelope",
+  "type": "object"
+}

AddedJul 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already signal readOnly/openWorld/idempotent/non-destructive. The description adds valuable behavioral context: the estimation method, the est-vs-EIA series, and the demo limitation that the freshest month's estimate is hidden. This goes well beyond what annotations convey.

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

Conciseness5/5

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

Two dense sentences with no filler. The main purpose is stated first, followed by methodology and the demo caveat. Every clause contributes useful information for invoking or interpreting the tool.

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?

Given zero parameters and the presence of an output schema, the description covers all necessary invocation context: units, frequency, series semantics, estimation approach, and the demo limitation. Nothing essential for a correct call 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?

With zero parameters, there is no parameter ambiguity to resolve. The description adds no parameter-specific meaning because none exists; the baseline for a no-parameter tool applies and is fully satisfied.

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?

Clearly identifies the tool as retrieving US dry natural gas production nowcasts in Bcf/d, with daily/monthly granularity. The methodology (YoY trend scaled from year-ago level, anchored to news) and comparison to EIA actuals further distinguish it from sibling nowcast tools like storage or weather.

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 description makes it obvious when to use this tool: whenever a production nowcast is needed, vs. storage/weather/market brief siblings. It does not explicitly list exclusions or alternative tools, but the domain-specific phrasing provides clear context for a zero-parameter retrieval tool.

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

All NatGasLens — US Natural Gas & Henry Hub Data 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?