DC Hub

Construction Pipeline

get_pipeline

Read-onlyIdempotent

Use when a user asks "what is being built / announced / permitted" in a market or by an operator — the forward-looking construction pipeline. 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

TableJSON 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

TableJSON Schema

Name	Required	Description
`data`	No	Same rows as `pipeline`
`count`	No	Rows returned in THIS response
`quota`	No	Caller quota state (remaining calls, tier).
`stats`	No	Aggregate pipeline stats
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`cite_as`	No	Ready-made attribution line
`success`	No	true when the query succeeded
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`pipeline`	No	Construction-pipeline projects
`by_quarter`	No	Projects per delivery quarter
`provenance`	No	Source, method, as_of, verification_counts, license, cite_as; quote it when citing.
`_front_door`	No	First-tool hint: plan_query(intent) returns the ordered plan.
`data_source`	No	Where the data comes from
`total_count`	No	Total projects matching
`_return_loop`	No	Next-session delta call (get_changes).
`last_updated`	No	Pipeline last refreshed
`site_evaluation_handoff`	No	Follow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026
RemovedSep 29, 2026

Changed2 schema fields changedAug 21, 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 changedAug 11, 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 changedJul 21, 2026

addedOutput schema / properties / _front_door

Added value: +{
+  "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"
+}

Changed5 schema fields changedJul 18, 2026

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

addedOutput schema / properties / site_evaluation_handoff / anyOf

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

changedOutput schema / properties / site_evaluation_handoff / description

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

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

Changed1 schema field changedJul 17, 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"
+    },
+    "_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": {
+      "additionalProperties": {},
+      "description": "Pre-built follow-up call (analyze_site / get_water_risk args) when the payload carries coordinates.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed11 schema fields changedJul 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"

Changed21 schema fields changedApr 29, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- removedInput schema / properties / country / default
```
Removed value: -""
```
- removedInput schema / properties / country / title
```
Removed value: -"Country"
```
- removedInput schema / properties / expected_completion_before / default
```
Removed value: -""
```
- removedInput schema / properties / expected_completion_before / title
```
Removed value: -"Expected Completion Before"
```
- removedInput schema / properties / limit / default
```
Removed value: -25
```
- addedInput schema / properties / limit / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / limit / minimum
```
Added value: +-9007199254740991
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / min_capacity_mw / default
```
Removed value: -0
```
- removedInput schema / properties / min_capacity_mw / title
```
Removed value: -"Min Capacity Mw"
```
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```
- removedInput schema / properties / offset / title
```
Removed value: -"Offset"
```
- removedInput schema / properties / operator / default
```
Removed value: -""
```
- removedInput schema / properties / operator / title
```
Removed value: -"Operator"
```
- removedInput schema / properties / status / default
```
Removed value: -"all"
```
- removedInput schema / properties / status / title
```
Removed value: -"Status"
```
- removedInput schema / title
```
Removed value: -"get_pipelineArguments"
```
- changedOutput schema / (root)
```
Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipelineOutput",
-  "type": "object"
-}New value: +null
```

Changed1 schema field changedApr 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_pipelineOutput",
+  "type": "object"
+}

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipelineOutput",
-  "type": "object"
-}New value: +null

Changed1 schema field changedMar 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_pipelineOutput",
+  "type": "object"
+}

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipelineOutput",
-  "type": "object"
-}New value: +null

First observedMar 6, 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 safety profile is covered. The description adds genuinely useful behavior: pagination bounds (limit 1-500, free 25; offset 0-100000) and empty-result recovery guidance ('relax status/operator/min_capacity_mw'). It doesn't add auth or rate-limit context, and the return-value explanation is redundant against the output schema, keeping it out of 5 territory.

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 and dense — the when-to-use trigger and worked example come first, and the call syntax is shown inline. Some redundancy remains: the Returns block restates what the output schema already provides, and the Params list largely mirrors the schema, so a few sentences don't fully earn their place.

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 a full output schema, the description covers everything an agent needs: trigger conditions, call example, param semantics, pagination limits, sibling disambiguation, and empty-result handling. Nothing material is left to inference.

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 baseline is 3, but the description adds invocation-level value: it enumerates the status values, gives sample operators/ISO codes, clarifies min_capacity_mw usage ('50 to filter hyperscale'), and explains expected_completion_before with a date example. It also flags the absence of a market param, steering parameter choice.

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 states a specific resource — 'the forward-looking construction pipeline' — with a concrete illustrative query and the exact call (get_pipeline country=US status=construction). It explicitly distinguishes itself from search_facilities and list_transactions, so an agent can route correctly without opening schemas.

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?

Opens with 'Use when...', names the disallowed uses ('Do NOT use for already-operational facilities... or for the M&A deal flow'), and points to the correct siblings. It even warns that there is no `market` parameter and offers the workaround (filter by country/operator or use search_facilities for a named market).

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

All DC Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Construction Pipeline

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources