Skip to main content
Glama

NatGasLens — US Natural Gas & Henry Hub Data

by com.natgaslens

get_us_natural_gas_chart

Read-onlyIdempotent

A ready-made chart of US natural gas fundamentals as a PNG image, the same card we publish to our own channel: LNG feedgas, the fundamental score with its signal contributions, GFS/ECMWF weather runs, EIA storage against the 5-year normal, a Gantt of liquefaction outages, the Henry Hub forward curve, or CFTC managed-money positioning. Use it when a human is going to look at the answer — the numbers behind every card are available as data from the other tools. kind is one of lng_feedgas, fundamental_score, weather_models, storage, lng_outages, forward_curve, cot_positioning. Requires a token: charts are the one thing demo scope cannot serve delayed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoWhich card to render: lng_feedgas, fundamental_score, weather_models, storage, lng_outages, forward_curve or cot_positioning.lng_feedgas

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint. The description adds authentication requirement (token) and scope limitation (demo cannot serve delayed). 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.

Conciseness5/5

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

Two sentences plus a clear line about kind and token. Every sentence adds essential information without redundancy. Front-loaded with core functionality.

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?

No output schema, but description thoroughly lists all chart types and their content. For a chart tool, it provides sufficient context about what the PNG will contain.

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?

Schema coverage is 100%, baseline 3. The description adds value by explaining all kind options and their context, plus token requirement, beyond the schema's description.

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 explicitly states it produces a PNG image chart of US natural gas fundamentals, listing specific cards. It clearly distinguishes from sibling data tools by noting that the chart is for human viewing.

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

Usage Guidelines5/5

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

Provides direct guidance: 'Use it when a human is going to look at the answer', and contrasts with data tools that provide numbers. This helps the agent choose appropriately.

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 toolsInspect
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