DC Hub: Data Center, Power Grid & Energy Intelligence

Construction Pipeline

get_pipeline

Read-onlyIdempotent

Retrieve announced, permitted, or under-construction data center projects filtered by country, operator, capacity, and expected completion date to identify coming capacity.

Instructions

Use this when the user asks what data centers are being built, announced or permitted in a market or by an operator. Example: "What data centers are under construction in Northern Virginia and when do they come online?" — get_pipeline country=US status=construction (there is no market parameter — filter by country/operator, or use search_facilities for a named market). Params: status one of "announced" | "permitted" | "construction" | "operational"; operator (e.g. "Equinix", "Digital Realty", "AWS"); country (ISO-2, e.g. "US", "DE"); min_capacity_mw (e.g. 50 to filter hyperscale); expected_completion_before (ISO date, e.g. "2027-01-01"); limit/offset for pagination. Returns: {projects:[{name, operator, capacity_mw, status, expected_commissioning, market_slug, country, lat, lon}], total, generated_at}. Do NOT use for already-operational facilities (use search_facilities) or for the M&A deal flow (use list_transactions). limit 1-500 (free 25), offset 0-100000. Empty data = no project matches: relax status/operator/min_capacity_mw.

Input Schema

Name	Required	Description
`limit`	No	Max results to return (1-500; default varies by tool)
`offset`	No	Pagination offset, 0-based (skip this many results)
`status`	No	Pipeline stage filter: announced, permitted, construction, or operational
`country`	No	ISO 3166-1 alpha-2 country code, e.g. US, DE, SG
`operator`	No	Operator/provider company name, e.g. Equinix, Digital Realty, AWS
`min_capacity_mw`	No	Minimum project power capacity filter in megawatts (MW), e.g. 50 for hyperscale
`expected_completion_before`	No	Only projects with expected commissioning before this ISO-8601 date (YYYY-MM-DD), e.g. 2027-01-01

Output Schema

Name	Required	Description	Default
`data`	No
`count`	No
`stats`	No
`cite_as`	No
`success`	No
`pipeline`	No
`by_quarter`	No
`data_source`	No
`total_count`	No
`last_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedv2.12.45Oct 22, 2026

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

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 / by_quarter / anyOf

Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / by_quarter / description
```
Removed value: -"Projects per delivery quarter"
```

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 / cite_as / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / cite_as / description
```
Removed value: -"Ready-made attribution line"
```

removedOutput schema / properties / count / anyOf

Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / count / description
```
Removed value: -"Rows returned in THIS response"
```

removedOutput schema / properties / data / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / data / description
```
Removed value: -"Same rows as `pipeline`"
```

removedOutput schema / properties / data_source / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / data_source / description
```
Removed value: -"Where the data comes from"
```

removedOutput schema / properties / last_updated / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / last_updated / description
```
Removed value: -"Pipeline last refreshed"
```

removedOutput schema / properties / pipeline / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / pipeline / description
```
Removed value: -"Construction-pipeline projects"
```

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."
-}

removedOutput schema / properties / stats / anyOf

Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / stats / description
```
Removed value: -"Aggregate pipeline stats"
```

removedOutput schema / properties / success / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / success / description
```
Removed value: -"true when the query succeeded"
```

removedOutput schema / properties / total_count / anyOf

Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / total_count / description
```
Removed value: -"Total projects matching"
```

Changed18 schema fields changedv2.12.43Oct 15, 2026

removedOutput schema / description

Removed 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."

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)."

addedOutput schema / properties / by_quarter

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Projects per delivery quarter"
+}

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."

addedOutput schema / properties / cite_as

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Ready-made attribution line"
+}

addedOutput schema / properties / count

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Rows returned in THIS response"
+}

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Same rows as `pipeline`"
+}

addedOutput schema / properties / data_source

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Where the data comes from"
+}

addedOutput schema / properties / last_updated

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Pipeline last refreshed"
+}

addedOutput schema / properties / pipeline

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Construction-pipeline projects"
+}

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."

addedOutput schema / properties / stats

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Aggregate pipeline stats"
+}

addedOutput schema / properties / success

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "true when the query succeeded"
+}

addedOutput schema / properties / total_count

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Total projects matching"
+}

Changed2 schema fields changedAug 30, 2026

removedInput schema / $schema

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

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"
+}

Changed11 schema fields changedv2.3.6Jul 2, 2026

addedInput schema / properties / country / description

Added value: +"ISO 3166-1 alpha-2 country code, e.g. US, DE, SG"

addedInput schema / properties / expected_completion_before / description

Added value: +"Only projects with expected commissioning before this ISO-8601 date (YYYY-MM-DD), e.g. 2027-01-01"

addedInput schema / properties / limit / description

Added value: +"Max results to return (1-500; default varies by tool)"

changedInput schema / properties / limit / maximum

Previous value: -9007199254740991New value: +500

changedInput schema / properties / limit / minimum

Previous value: --9007199254740991New value: +1

addedInput schema / properties / min_capacity_mw / description

Added value: +"Minimum project power capacity filter in megawatts (MW), e.g. 50 for hyperscale"

addedInput schema / properties / offset / description

Added value: +"Pagination offset, 0-based (skip this many results)"

changedInput schema / properties / offset / maximum

Previous value: -9007199254740991New value: +100000

changedInput schema / properties / offset / minimum

Previous value: --9007199254740991New value: +0

addedInput schema / properties / operator / description

Added value: +"Operator/provider company name, e.g. Equinix, Digital Realty, AWS"

addedInput schema / properties / status / description

Added value: +"Pipeline stage filter: announced, permitted, construction, or operational"

First observedv2.1.19Jun 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds real behavioral context: pagination bounds with a free-tier limit (25), the empty-result interpretation ('no project matches: relax status/operator/min_capacity_mw'), and the return shape. It stops short of describing rate limits or freshness of the pipeline data.

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?

Front-loaded with use case and example, then params, returns, exclusions, and limits in a compact sequence. Dense but mostly each clause earns its place; the return-shape enumeration is slightly redundant given an output schema exists.

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 7-param read tool with 100% schema coverage, annotations, and an output schema, the description covers selection, alternatives, parameter nuances, pagination limits, and empty-result handling. Nothing an agent needs to invoke it correctly 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 coverage is 100%, so the schema baseline is 3, but the description adds value beyond it: it explicitly states there is no `market` parameter and how to work around it, gives operator examples, clarifies min_capacity_mw as a hyperscale filter, and pairs expected_completion_before with an ISO date example.

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 resource (data center construction/announcement/permit pipeline) with a concrete verb ('get') and an inline example question it answers. It also explicitly names what it is NOT for (operational facilities, M&A deal flow), separating it from search_facilities and list_transactions.

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 explicit when-to-use (user asks what is being built/announced/permitted), a worked example, and when-not-to-use with the alternative tool named for each case. It even flags a missing parameter and routes the agent to search_facilities for named-market queries.

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

Deploy Server