NatGasLens — US Natural Gas & Henry Hub Data

get_us_natural_gas_news_context

Read-onlyIdempotent

Recent events moving US natural gas: LNG plant outages and restarts, Gulf storms, and market-wide stories, each with its source link. Pro scope adds our reading of every story — bullish / bearish / neutral, a 1-5 strength score explicitly gated on whether the story reaches Henry Hub (US liquefaction runs near its ceiling, so foreign demand shocks often move JKM and TTF but not the domestic balance) and whether it is already priced in, plus machine-readable facts (plant, status, Bcf/d, dates) and a plain-English summary. Demo scope returns the same reading for stories older than a week and headlines for the fresh ones.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Look-back window in days for events to consider.
`limit`	No	Maximum number of events to return, newest first.

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.

Changed7 schema fields changedJul 28, 2026

addedInput schema / properties / days / description

Added value: +"Look-back window in days for events to consider."

addedInput schema / properties / days / maximum
```
Added value: +90
```
addedInput schema / properties / days / minimum
```
Added value: +1
```

addedInput schema / properties / limit / description

Added value: +"Maximum number of events to return, newest first."

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / 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

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds detail about the scoring logic (gating on Henry Hub relevance and whether events are priced in) and the output variations between scopes, which goes beyond the annotations without contradicting them.

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

Conciseness3/5

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

The description is somewhat verbose and rambling, with a lengthy parenthetical about Henry Hub and JKM/TTF that could be condensed. However, it is still structured logically and conveys all key information without being excessively long.

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?

The description explains what the tool returns for both Pro and Demo scopes, including the type of analysis (bullish/bearish/neutral, strength score) and additional facts. Since no output schema is provided, this description compensates well by outlining the expected output structure.

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 schema provides complete descriptions for both parameters (days and limit) with ranges and defaults. The description does not add any extra meaning to these parameters, so the baseline of 3 is appropriate given the 100% schema coverage.

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 clearly states the tool's purpose: retrieving recent events affecting US natural gas, including specific types (LNG outages, Gulf storms, market stories) and that each event includes a source link. The resource and action are unambiguous.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this tool over sibling tools. It explains the difference between Pro and Demo scopes but offers no guidance on selecting this tool vs. others like get_us_natural_gas_market_brief or get_us_natural_gas_fundamental_score.

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?