Skip to main content
Glama

DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber

by cloud.dchub

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (1-500; default varies by tool)
offsetNoPagination offset, 0-based (skip this many results)
statusNoPipeline stage filter: announced, permitted, construction, or operational
countryNoISO 3166-1 alpha-2 country code, e.g. US, DE, SG
operatorNoOperator/provider company name, e.g. Equinix, Digital Realty, AWS
min_capacity_mwNoMinimum project power capacity filter in megawatts (MW), e.g. 50 for hyperscale
expected_completion_beforeNoOnly projects with expected commissioning before this ISO-8601 date (YYYY-MM-DD), e.g. 2027-01-01

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed5 schema fields changed
    • 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"
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed5 schema fields changed
    • 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"
  5. Changed1 schema field changed
    • 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"
+}
  6. Changed11 schema fields changed
    • 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"
  7. Changed21 schema fields changed
    • 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
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_pipelineOutput",
+  "type": "object"
+}
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipelineOutput",
-  "type": "object"
-}New value: +null
  10. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_pipelineOutput",
+  "type": "object"
+}
  11. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipelineOutput",
-  "type": "object"
-}New value: +null
  12. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered elsewhere. The description goes beyond by documenting the exact return shape ({projects:[...], total, generated_at}) and adding synonym context ('under construction', 'come online') that helps a model map user phrasing to this tool rather than a sibling.

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?

It's a long paragraph, but every sentence earns its place. The structure front-loads the core use case and example before diving into parameters, and distinct logical blocks (purpose, params, return, exclusions) are present. The only reason it's not a 5 is that the parameter documentation could have been left to the schema (which covers it) to make the description more skimmable, but the compression is still strong.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only pipeline tool with an output schema present, it covers all the bases: parameter list, return contract, exclusions, and pagination via limit/offset. It could theoretically add details on default sort order or maximum date ranges for expected_completion_before, but those are minor given the output schema fills the gap. Feels complete for its purpose.

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 baseline is 3. The description earns the extra point by listing the fixed status enum inline, giving concrete example values for operator ('Equinix', 'Digital Realty'), clarifying ISO-2 format for country, and explaining the expected_completion_before date format. This compensates for the fact that the schema itself does not define enums and saves the model a trial-and-error call.

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 specific verb+resource ('what is being built / announced / permitted') and clearly frames get_pipeline as the 'forward-looking construction pipeline.' It proactively differentiates from siblings by stating what it is not (no `market` param, use search_facilities for a named market), leaving no ambiguity about its scope.

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?

It gives an explicit 'Use when' rule, a full worked example with status=construction, and then explicit 'Do NOT use' guidance for operational facilities (search_facilities) and M&A deal flow (list_transactions). This is the gold standard for routing an agent to the correct tool.

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

All DC Hub — Data Center Site Selection & Colocation: Electricity, Power Grid, Gas, Fiber toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes despite some thematic overlap, and each description includes explicit 'Do NOT use' guidance to prevent misselection. However, a few pairs like search_intelligence vs semantic_search are nearly identical in function, and the sheer number of tools increases the chance of selecting the wrong one without careful reading.

Naming Consistency4/5

The vast majority of tools follow a predictable 'get_*' prefix for data reads, and many others use verb_noun patterns (analyze_*, rank_*, save_*, set_*). There are a handful of outliers like ai_capacity_index, grid_transition_radar, and site_selection_canvas that break the pattern, but overall the conventions are consistent enough for an agent to infer meaning.

Tool Count2/5

With 82 tools, this server is extremely heavy compared to typical MCP servers (3-15 tools). While the domain is broad, many tools serve narrow sub-purposes and could be consolidated (e.g., multiple site-scoring variants, multiple grid telemetry endpoints). The count overwhelms an agent's ability to choose efficiently and feels like over-fragmentation rather than necessary granularity.

Completeness4/5

The tool surface covers the full lifecycle of data-center siting intelligence: site analysis, grid, fiber, water, climate, tax, permitting, deals, news, saved-site management, and meta-planning. Minor gaps exist (e.g., no delete or update operations for saved sites), but the core workflows are well-supported and the descriptions are comprehensive.

Resources