Skip to main content
Glama
azmartone67

DC Hub — Data Center & Energy Intelligence

Gas Index (DCGI)

get_gas_index
Read-onlyIdempotent

Retrieve a U.S. state's natural-gas suitability score (DCGI) and verdict, including the EIA price series used. Unpriceable states return UNSCORED, not a low score.

Instructions

Data Center Gas Index (DCGI) — the per-US-state natural-gas suitability score. ★ WITHDRAWN 2026-08-08, RESTORED 2026-08-30 after all three defective terms were repaired: the 20-point interstate-share term was case-blind against EIA TYPEPIPE and scored ~0 for every state (122 -> 17,571 segments now counted); the price was chosen by a non-deterministic tie-break across the EIA industrial (PIN) and electric-power (PEU) series, which carry different margins; and nine states including Texas ran on a hardcoded cost constant because the price loader dropped them on a case-sensitive name lookup. ★ DO NOT COMPARE a DCGI figure published before 2026-08-08 with one published now — they are different indices; the full record is at /api/v1/dcgi/methodology under corrections. A state that cannot be priced comes back verdict UNSCORED with dcgi null and an unscored_reason, never a placeholder score, so treat UNSCORED as absence and not as a low score. gas_price_series names which EIA series answered each state. ★ STILL WITHDRAWN and NOT restored by this: every gas-fired $/MWh figure — a separate defect from the same audit. Use get_gas_intelligence for pipeline, operator and parent-midstream data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies by tool)
stateNoUS state abbreviation, e.g. TX, VA, AZ. Returns the DCGI score and verdict, plus `gas_price_series` naming which EIA series priced the state. A state that cannot be priced comes back verdict UNSCORED with dcgi null and an `unscored_reason` — absence, not a low score. Withdrawn 2026-08-08, restored 2026-08-30: do NOT compare against a figure published before 2026-08-08. Use get_gas_intelligence for the per-state pipeline and operator brief

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.
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already list readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds substantial behavioral context: the withdrawal/restoration history, the three repaired defects, the UNSCORED-vs-low-score semantics, and the explicit guidance that UNSCORED means absence rather than a poor score. It also names the gas_price_series field as a way to see which EIA series priced the state.

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 long, but most sentences earn their place because the tool history is genuinely complex. It is front-loaded with the core purpose, then gives correction history, data-interpretation warnings, and sibling routing. Some redundancy exists between the main description and the state parameter description, so it is not maximally concise.

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 withdrawal/restoration history, scoring semantics, and a sibling-data boundary, the description is remarkably complete. Combined with the output schema, the agent has enough context to call the tool correctly, interpret UNSCORED results, avoid comparing incompatible values, and route pipeline-related queries to get_gas_intelligence.

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 description coverage is 100%, so the schema already documents both parameters. The description and state parameter go beyond the schema by explaining what the response includes (DCGI score, verdict, gas_price_series, unscored_reason) and how to interpret UNSCORED. The limit parameter receives no additional description, but that is acceptable given the schema already defines its range and behavior.

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 precise verb-plus-resource statement: it provides the per-US-state Data Center Gas Index (DCGI) natural-gas suitability score. It also clearly differentiates itself from get_gas_intelligence by stating that pipeline, operator, and parent-midstream data belong to that sibling tool, and it warns that gas-fired $/MWh figures are not restored here.

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?

The description gives explicit routing guidance: use get_gas_intelligence for pipeline, operator, and parent-midstream data, and avoid treating restored DCGI values as comparable to pre-2026-08-08 figures. It also clearly marks gas-fired $/MWh values as still withdrawn, telling the agent what this tool does NOT cover.

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

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