DC Hub: Data Center, Power Grid & Energy Intelligence

Get Infra Projects

get_infra_projects

Read-onlyIdempotent

Query planned, proposed, approved or under-construction US gas pipeline and ISO transmission projects by state, status, capacity, voltage and in-service date.

Instructions

Use this when the user asks what gas pipeline or transmission line projects are planned, proposed, approved or under construction — the forward build-out, not the existing network. e.g. "which interstate gas pipelines are under construction into Louisiana?", "what 345 kV transmission projects are planned in PJM by 2030?", "what new projects appeared since last month?". COVERS: (1) natural gas pipeline projects US-wide from the EIA natural gas pipeline projects list (public domain) — operator, status (Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed), states crossed, capacity in MMcf/d, miles, cost in $M, diameter, FERC/state docket, in-service year; (2) transmission projects from five ISOs' own project lists — ERCOT (TPIT), PJM (RTEP), MISO (MTEP Appendix A), SPP (STEP) and ISO-NE (RSP list); NOT CAISO or NYISO, and not utilities outside those ISOs. Each ISO publishes a different grain (an upgrade or facility, not a whole project), so a row count is a count of upgrades. Answers "what gas pipelines are being built into Louisiana, how much capacity do they add, and when do they enter service". Try: get_infra_projects type=gas_pipeline state=LA status=Construction.

Input Schema

Name	Required	Description
`type`	No	Which project list: gas_pipeline (EIA, US-wide), transmission (ERCOT TPIT, Texas only) or all (default)
`limit`	No	Max results to return (1-500; default varies by tool)
`state`	No	US state abbreviation, e.g. TX or LA. Gas projects match any state they cross; transmission projects are all TX
`min_kv`	No	Transmission only: minimum voltage in kilovolts (kV), e.g. 345. With type=all it narrows to transmission projects
`status`	No	Status, case-insensitive; comma list allowed. Gas: Announced, Pre-applied, Applied, Approved, Construction, On Hold, Completed. Transmission: Planned, Conceptual, Under Construction, Completed, Cancelled
`new_since`	No	Only projects DC Hub first saw on or after this date (YYYY-MM-DD). The initial backfill is never counted as new
`min_capacity`	No	Gas only: minimum pipeline capacity in million cubic feet per day (MMcf/d), e.g. 1000. With type=all it narrows to gas projects
`in_service_after`	No	Only projects entering service on or after this date (YYYY-MM-DD or YYYY). Gas compares the in-service year; transmission the actual, else projected, in-service date
`include_delisted`	No	Also return projects the latest source release no longer lists (completed, withdrawn or dropped). Default false
`in_service_before`	No	Only projects entering service on or before this date (YYYY-MM-DD or YYYY)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.12.45Oct 22, 2026

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```

removedOutput schema / description

Removed value: -"DC Hub envelope: tool data fields ride at the top level beside these keys."

removedOutput schema / properties / _entity

Removed value: -{
-  "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
-  "type": "string"
-}

removedOutput schema / properties / _front_door

Removed value: -{
-  "additionalProperties": {},
-  "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / _return_loop

Removed value: -{
-  "additionalProperties": {},
-  "description": "Next-session delta call (get_changes).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / citation

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    {
-      "type": "string"
-    }
-  ],
-  "description": "How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
-}

removedOutput schema / properties / provenance

Removed value: -{
-  "additionalProperties": {},
-  "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / quota

Removed value: -{
-  "additionalProperties": {},
-  "description": "Caller quota state (remaining calls, tier).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / site_evaluation_handoff

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    }
-  ],
-  "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
-}

Changed8 schema fields changedv2.12.43Oct 15, 2026

changedOutput schema / description

Previous value: -"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."New value: +"DC Hub envelope: tool data fields ride at the top level beside these keys."

changedOutput schema / properties / _entity / description

Previous value: -"Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest."New value: +"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."

changedOutput schema / properties / _front_door / description

Previous value: -"In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan."New value: +"First-tool hint: plan_query(intent) returns the ordered plan."

changedOutput schema / properties / _return_loop / description

Previous value: -"Suggested next-session delta call (get_changes since=24h) so you pull only what changed."New value: +"Next-session delta call (get_changes)."

changedOutput schema / properties / citation / description

Previous 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."New value: +"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."

changedOutput schema / properties / provenance / description

Previous value: -"Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing."New value: +"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."

changedOutput schema / properties / quota / description

Previous value: -"Caller quota state (remaining calls, tier) when available."New value: +"Caller quota state (remaining calls, tier)."

changedOutput schema / properties / site_evaluation_handoff / description

Previous value: -"Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries."New value: +"Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."

Addedv2.12.20Sep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is low. The description adds real behavioral context beyond them: provenance (EIA public domain, five ISO project lists), a critical grain caveat that a row count is a count of upgrades rather than whole projects, and the delisting/source-release behavior implied by include_delisted.

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?

Long but deliberately structured: trigger statement first, then COVERS, then NOT, then a worked example, so the load-bearing guidance is front-loaded. The coverage block is dense but each clause (sources, fields, grain) carries information an agent needs to interpret results correctly.

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?

With an output schema present, return values need not be explained, and the description covers everything else: what is included and excluded, source provenance, per-source grain, status vocabularies, and units. Nothing an agent needs to invoke or interpret this 10-parameter, zero-required tool is missing.

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 carries parameter documentation and the baseline is 3. The description still adds value by enumerating status vocabularies, giving unit meaning (MMcf/d, $M, kV), explaining the per-ISO grain of transmission rows, and showing a concrete invocation pattern (type=gas_pipeline state=LA status=Construction).

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 (retrieving planned/proposed/approved/under-construction infrastructure projects) and immediately scopes it against the existing network, so it is distinguishable from sibling tools like get_pipeline or get_infrastructure. The two coverage categories (EIA gas pipelines, five ISO transmission lists) are named explicitly with their source lists.

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 explicit when-to-use triggers ('what ... are planned, proposed, approved or under construction — the forward build-out, not the existing network') and sample queries, plus negative scope (NOT CAISO or NYISO, not utilities outside those ISOs). It stops short of naming the alternative sibling tool an agent should pick for the existing network, leaving that routing to inference.

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

Deploy Server