Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

Get Gas Economics

get_gas_economics
Read-onlyIdempotent

Get gas-fired power input costs for a US data-center market: Henry Hub spot, regional basis differential, delivered industrial/electric tariff in $/MMBtu, source-labeled. Pass market slug.

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"). ★ WITHDRAWN 2026-08-08: the gas-to-grid levelized cost ($/MWh across CCGT/peaker heat-rate scenarios) is NO LONGER RETURNED. Five surfaces published a $/MWh for the same market on the same day up to 5.5x apart because each chose the burner-tip price by a different rule, with no sanity gate — this endpoint served a physically impossible $6.73/MWh for Phoenix stamped data_basis: "live". The heat-rate arithmetic was correct; the input price selection was not. The $/MMBtu layers are sourced and still returned; gas_to_grid_status carries the reason. DO NOT quote a cached $/MWh figure, and do not derive one yourself from the $/MMBtu without saying that you did. Do NOT use for the electricity grid fuel mix (use get_grid_data).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoMarket slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank
heat_rate_btu_per_kwhNoOptional custom generator heat rate in Btu/kWh for the gas-to-grid $/MWh scenario, e.g. 6800 (avg CCGT)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
quotaNoCaller quota state (remaining calls, tier) when available.
_entityNoPayload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.
citationNoMachine-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.
provenanceNoCollection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
_front_doorNoIn-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
site_evaluation_handoffNoPre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries.
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavioral traits: the withdrawal of the gas-to-grid levelized cost field, the reason (a physically impossible $6.73/MWh for Phoenix), that $/MMBtu layers are still returned, and that gas_to_grid_status carries the reason. This is substantial context not provided by annotations.

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?

The description is lengthy but well-structured, front-loading the primary purpose and then using a clear withdrawal warning. Every sentence contributes value, though it could be tightened without losing essential safety information.

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?

For a tool with a withdrawn feature and significant safety implications, the description covers purpose, usage, alternatives, return status, and caveats about data reliability. It is complete even with an output schema present, because it adds critical warnings not available in structured fields.

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% for both parameters, with market already explaining slug examples and valid source. The description adds no new parameter semantics beyond what the schema provides, so the baseline of 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?

The description clearly states the tool's function: providing behind-the-meter/gas-fired power inputs (Henry Hub spot, regional basis differential, delivered gas tariff in $/MMBtu) for US data-center markets. It distinguishes itself from get_grid_data by explicitly noting it is not for electricity grid fuel mix.

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?

Explicit usage guidance is provided: pass market=<slug> with examples, and a clear exclusion 'Do NOT use for the electricity grid fuel mix (use get_grid_data)'. It also warns against quoting cached $/MWh figures or deriving them without disclosure, and mentions gas_to_grid_status for the reason.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azmartone67/dchub-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server