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

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: it returns historical comparisons, 'Pro scope adds today's live prices and curve-shape read', and includes a disclaimer ('Market context, not investment advice'). No contradictions.

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?

Description is dense but efficient; it front-loads the main output and then adds details about Pro scope. Could be slightly more concise, but no extraneous sentences.

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?

Output schema exists, annotations are rich. The description covers key aspects: what data is returned, historical context, and Pro scope features. It provides a complete picture for an agent to decide to use this tool.

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?

Only one parameter (months) with schema coverage 100% (description already states 'How many delivery months...'). The tool description does not add additional parameter semantics beyond the schema, so baseline 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?

Clearly states the tool returns 'Henry Hub natural gas futures forward curve by delivery month' with price, session move, volume, and historical comparisons. The description differentiates from siblings by specifying the unique data (forward curve) vs. other tools (e.g., COT, storage, 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?

Does not explicitly state when to use or not use this tool, but the sibling tools are all distinct (e.g., weather, storage, production), so context makes it clear. A brief usage hint would improve it.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool addresses a distinct aspect of natural gas data: fundamental score, production nowcast, and storage nowcast. There is no functional overlap, and agents can easily differentiate them.

Naming Consistency5/5

All tools follow a consistent 'get_us_natural_gas_<specific_measure>' pattern, using snake_case and clear descriptive names. The naming is uniform and predictable.

Tool Count4/5

Three tools cover key indicators for natural gas monitoring. While the set is concise, it avoids bloat and each tool adds significant value. A slight increase might be justified, but the current count is appropriate for the focused scope.

Completeness4/5

The tools provide core supply and demand indicators (production, storage, and a composite score incorporating demand). Minor gaps like a separate demand tool exist, but the composite score partially addresses them, making the surface fairly complete for monitoring purposes.

Resources

Need Help?