DC Hub Intelligence

Get Gas Economics

get_gas_economics

Read-onlyIdempotent

Retrieve gas-fired power inputs by market slug for a US data-center market: Henry Hub spot, basis differential, delivered gas tariff ($/MMBtu), and gas-to-grid fuel cost ($/MWh) by heat rate.

Instructions

Behind-the-meter / gas-fired power inputs for a US data-center market: Henry Hub spot, regional basis differential, and the delivered industrial + electric gas tariff ($/MMBtu), each with its own source label. Pass market= (e.g. "northern-virginia", "dallas", "phoenix"). Also returns the gas-to-grid fuel cost ($/MWh across CCGT/peaker heat-rate scenarios) — ★ WITHDRAWN 2026-08-08, RESTORED 2026-09-27 under one burner-tip price rule now used by every surface: EIA electric-power (PEU) delivered gas only, trailing-12-month mean over one window shared by every state (negative months included), published only when at least 9 of 12 months are reported and the mean is above $0 and at most $20/MMBtu. burner_tip carries the price, window, months reported and monthly min/max; a state that fails the rule comes back with null scenarios and burner_tip.reason (EIA withholds the monthly price for several states, e.g. AZ, GA, FL), never a substitute price; if the backend switch is ever turned off again, gas_to_grid_status carries that reason. ★ DO NOT COMPARE a $/MWh published before 2026-09-27 with one published now — each surface then picked the price its own way, up to 5.5x apart. Do not derive a $/MWh yourself from the $/MMBtu layers for a withheld state without saying that you did. Do NOT use for the electricity grid fuel mix (use get_grid_data).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`market`	Yes	Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank
`heat_rate_btu_per_kwh`	No	Optional custom generator heat rate in Btu/kWh for the gas-to-grid $/MWh scenario, e.g. 6800 (avg CCGT)

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier) when available.
`_entity`	No	Payload class discriminator (e.g. facility\|market\|iso_grid\|queue_results\|deal\|report\|response) — branch on this before parsing the rest.
`citation`	No	Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself.
`provenance`	No	Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
`_front_door`	No	In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
`_return_loop`	No	Suggested next-session delta call (get_changes since=24h) so you pull only what changed.
`site_evaluation_handoff`	No	Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / required
```
Added value: +[
+  "market"
+]
```

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed5 schema fields changedv2.3.20Aug 14, 2026

removedOutput schema / properties / citation / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / citation / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]

changedOutput schema / properties / citation / description

Previous value: -"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload."New value: +"Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself."

removedOutput schema / properties / citation / properties
```
Removed value: -{}
```
removedOutput schema / properties / citation / type
```
Removed value: -"object"
```

Changed1 schema field changedv2.3.12Jul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "DC Hub envelope: structuredContent mirrors the JSON payload in content[0].text — tool-specific data fields ride at the top level alongside these envelope keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.",
+      "type": "string"
+    },
+    "_front_door": {
+      "additionalProperties": {},
+      "description": "In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.",
+      "properties": {},
+      "type": "object"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Suggested next-session delta call (get_changes since=24h) so you pull only what changed.",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "additionalProperties": {},
+      "description": "Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload.",
+      "properties": {},
+      "type": "object"
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier) when available.",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        }
+      ],
+      "description": "Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedv2.3.6Jul 2, 2026

addedInput schema / properties / heat_rate_btu_per_kwh / description

Added value: +"Optional custom generator heat rate in Btu/kWh for the gas-to-grid $/MWh scenario, e.g. 6800 (avg CCGT)"

addedInput schema / properties / market / description

Added value: +"Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank"

Addedv2.3.1Jun 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only establish readOnly/idempotent, and the description adds substantial operative behavior: the burner-tip pricing rule (EIA PEU delivered gas, trailing-12-month mean, one shared window, negative months included), the publication gate (≥9 of 12 months, mean >$0 and ≤$20/MMBtu), the failure mode (null scenarios plus burner_tip.reason, never a substitute price, with AZ/GA/FL called out), the gas_to_grid_status kill-switch field, and the cross-version comparability warning (up to 5.5x). This is exactly the kind of context annotations cannot carry.

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 purpose is front-loaded and the ★ markers make the critical warnings scannable, but the description carries a changelog (WITHDRAWN 2026-08-08, RESTORED 2026-09-27), a full statistical rule, and repeated escalation in caps. Much of this is genuinely load-bearing, yet the density of historical provenance crowds out the parameter guidance an agent also needs.

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?

For a tool with rich annotations, a 100%-covered schema, and an output schema, this covers the operational traps (withheld states, comparability across versions, do-not-derive advice) that would otherwise cause silent errors. The remaining gap is the optional heat_rate_btu_per_kwh control and how a custom heat rate interacts with the default CCGT/peaker scenarios, which the description ignores.

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?

Schema description coverage is 100%, so baseline is 3. The description restates the market slug and its examples (already in the schema) and never mentions heat_rate_btu_per_kwh, so it adds essentially no semantic value beyond the structured field definitions.

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?

States a specific verb+resource with its scope: behind-the-meter/gas-fired inputs for a US data-center market, enumerating Henry Hub spot, basis differential, delivered industrial+electric tariff, and gas-to-grid $/MWh. It actively distinguishes itself from siblings by naming get_grid_data as the wrong tool for grid fuel mix, so an agent can place it against get_gas_index/get_energy_prices without opening a schema.

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?

Gives a clear trigger (US data-center market gas economics), the exact invocation form market=<slug> with examples, and the source of valid slugs (rank_markets / get_market_dcpi_rank). It also states an explicit exclusion (grid fuel mix → get_grid_data). It does not, however, route against the adjacent gas tools (get_gas_index, get_gas_intelligence, get_gas_price-adjacent siblings), which are the most likely mis-selections.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server