NatGasLens — US Natural Gas & Henry Hub Data

get_henry_hub_forward_curve

Read-onlyIdempotent

Henry Hub natural gas futures forward curve by delivery month: price, session move, volume, and the same months a week, a month and a year ago for year-over-year context. Pro scope adds today's live prices and the curve-shape read — how much of the front-end move reached the far end and how unusual that pass-through is against two years of comparable days (a front-only move is a near-term balance story, a parallel shift is not). Market context, not investment advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`months`	No	How many delivery months of the curve to return, starting from the front month.

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.

Changed4 schema fields changedJul 28, 2026

addedInput schema / properties / months / description

Added value: +"How many delivery months of the curve to return, starting from the front month."

addedInput schema / properties / months / maximum
```
Added value: +36
```
addedInput schema / properties / months / minimum
```
Added value: +1
```

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 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already signal a safe, idempotent read operation, and the description adds the Pro-scope behavior (live prices and curve-shape read) plus a not-investment-advice disclaimer. This supplements the structured metadata without contradicting it.

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 stays informative without excessive length. The additional Pro-scope and disclaimer sentences earn their place by clarifying expected behavior.

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 a single optional parameter, complete schema coverage, a rich output schema, and annotations covering safety/idempotency, the description provides all needed context. Nothing critical is missing.

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 only parameter, months, is fully documented in the schema with a clear description. The tool description adds no new parameter detail, so schema coverage carries the burden.

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 names a specific resource (Henry Hub natural gas futures forward curve) and details exactly what is returned: price, session move, volume, and prior-year comparisons. This clearly differentiates it from sibling tools about storage, weather, and production.

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?

The content makes it obvious this is the tool for forward-curve data, but there is no explicit when-to-use guidance or comparison with siblings. Usage is implied 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 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?