NatGasLens — US Natural Gas & Henry Hub Data

get_us_lng_feedgas

Read-onlyIdempotent

Daily LNG feedgas for US liquefaction terminals (Bcf/d) — the export pull on the domestic natural gas balance, nowcast from pipeline nominations on the terminals' electronic bulletin boards (split across operators, no single public source). Returns today's total with a regime label (loose / below_normal / normal / tight) measured against nameplate capacity and the 30-day mean, utilization, and the daily history. Pro scope adds the per-terminal breakdown, the measured-vs-estimated split and movers — who drove the change versus yesterday. Demo scope returns the same fields, breakdown included, as of a week ago.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`history_days`	No	How many days of daily feedgas history to return (1-400).

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 / history_days / description

Added value: +"How many days of daily feedgas history to return (1-400)."

addedInput schema / properties / history_days / maximum
```
Added value: +400
```
addedInput schema / properties / history_days / 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/5.0

Behavior5/5

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

This goes well beyond the readOnly/idempotent annotations by revealing the nowcast nature, the fragmented data source ('split across operators, no single public source'), the difference between measured and estimated values, the Pro/Demo access scope, and how the regime label is computed. No annotation conflict exists.

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?

The description is long but every sentence contributes unique operational detail: data source, return fields, regime definition, Pro scope, and Demo scope. It is front-loaded with the core identity of the tool and avoids filler, making it dense but efficient.

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 the tool's complexity, the presence of an output schema, and rich annotations, this description is complete. It explains the data provenance, what the return contains, how the regime label is determined, what Pro vs Demo scope changes, and the single parameter's role. Nothing essential for selecting or invoking the tool 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?

With only one optional parameter and 100% schema description coverage ('How many days of daily feedgas history to return (1-400)'), the schema already fully documents the parameter. The description mentions daily history but does not need to add further parameter details; the baseline of 3 applies.

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-plus-resource ('Daily LNG feedgas for US liquefaction terminals') and clearly enumerates what is returned: today's total, regime label, utilization, and daily history. It naturally differentiates itself from siblings such as get_us_lng_plant_outages by focusing on the export pull on the domestic gas balance rather than outages or production.

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 does not explicitly name alternative tools or state 'use this instead of X', but it provides strong contextual signals: it is the feedgas nowcast tool, sourced from pipeline nominations, and appropriate whenever LNG terminal feedgas or export pull is the subject. The Pro/Demo scope explanation also clarifies what level of detail a caller can expect, though it does not list exclusions.

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?