Skip to main content
Glama

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

by cloud.dchub

M&A Transactions

list_transactions
Read-onlyIdempotent

M&A and capital transactions in the data center sector — 2,100+ tracked deals (2019-present), each with its disclosed value where public (many private deals are undisclosed). Returns deal name, buyer, seller, value, date, market, target operator, type (acquisition/JV/refinance/recap). Filter by date range (date_from/date_to, ISO-8601), min_value_usd, region, buyer, or seller. Answers "which data-center deals closed this year", "what was that acquisition worth". Try: list_transactions date_from=2026-01-01 min_value_usd=1000000000. There is no year parameter — use date_from/date_to. Broad M&A and capital-deal flow with filters; do NOT use for hyperscaler-specific lease/PPA/JV activity (use hyperscaler_deals) or a single-deal post-mortem (use deal_autopsy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyerNoFilter by acquiring company name, e.g. Blackstone, KKR, Digital Realty
limitNoMax results to return (1-500; default varies by tool)
offsetNoPagination offset, 0-based (skip this many results)
regionNoGeographic region filter, e.g. us, eu, apac, americas
sellerNoFilter by selling/target company name, e.g. CyrusOne
date_toNoLatest deal date, ISO-8601 (YYYY-MM-DD)
date_fromNoEarliest deal date, ISO-8601 (YYYY-MM-DD)
deal_typeNoDeal type filter, e.g. acquisition, jv, refinance, recap
max_value_usdNoMaximum disclosed deal value in US dollars
min_value_usdNoMinimum disclosed deal value in US dollars, e.g. 1000000000 for $1B+

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoServing note
tierNoTier the response was served at
countNoRows returned in THIS response
quotaNoCaller quota state (remaining calls, tier) when available.
cachedNoWhether the response was served from cache
_entityNoPayload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest.
successNotrue when the deal query succeeded
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.
data_sourceNoWhere the deal set comes from
total_countNoTotal deals matching the filter
total_valueNoAggregate disclosed value across the returned set (null when not computed)
_return_loopNoSuggested next-session delta call (get_changes since=24h) so you pull only what changed.
transactionsNoM&A / capital-transaction rows
total_value_unitNoUnit of total_value
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. Changed16 schema fields changed
    • 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: +"Data-center M&A / capital transactions: `transactions` rows with buyer/seller/value/date — alongside the DC Hub envelope keys."
    • addedOutput schema / properties / cached
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Whether the response was served from cache"
+}
    • addedOutput schema / properties / count
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Rows returned in THIS response"
+}
    • addedOutput schema / properties / data_source
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Where the deal set comes from"
+}
    • addedOutput schema / properties / note
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Serving note"
+}
    • 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"
    • addedOutput schema / properties / success
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "true when the deal query succeeded"
+}
    • addedOutput schema / properties / tier
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Tier the response was served at"
+}
    • addedOutput schema / properties / total_count
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Total deals matching the filter"
+}
    • addedOutput schema / properties / total_value
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Aggregate disclosed value across the returned set (null when not computed)"
+}
    • addedOutput schema / properties / total_value_unit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Unit of total_value"
+}
    • addedOutput schema / properties / transactions
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "buyer": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Acquirer"
+          },
+          "date": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Deal date (ISO-8601)"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Deal id"
+          },
+          "market": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Market the deal touches"
+          },
+          "mw": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Capacity involved, MW, when disclosed"
+          },
+          "region": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Region (us | eu | apac | americas …)"
+          },
+          "seller": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Seller / target"
+          },
+          "type": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "acquisition | jv | refinance | recap …"
+          },
+          "value": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Deal value when disclosed (see value_unit)"
+          },
+          "value_confirmed": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Whether the value is confirmed vs reported"
+          },
+          "value_display": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Human-formatted value, e.g. \"$9.2B\" or \"Undisclosed\""
+          },
+          "value_unit": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Unit of `value` (e.g. USD)"
+          },
+          "year": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Deal year"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "M&A / capital-transaction rows"
+}
  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. Changed14 schema fields changed
    • addedInput schema / properties / buyer / description
      Added value: +"Filter by acquiring company name, e.g. Blackstone, KKR, Digital Realty"
    • addedInput schema / properties / date_from / description
      Added value: +"Earliest deal date, ISO-8601 (YYYY-MM-DD)"
    • addedInput schema / properties / date_to / description
      Added value: +"Latest deal date, ISO-8601 (YYYY-MM-DD)"
    • addedInput schema / properties / deal_type / description
      Added value: +"Deal type filter, e.g. acquisition, jv, refinance, recap"
    • 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 / max_value_usd / description
      Added value: +"Maximum disclosed deal value in US dollars"
    • addedInput schema / properties / min_value_usd / description
      Added value: +"Minimum disclosed deal value in US dollars, e.g. 1000000000 for $1B+"
    • 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 / region / description
      Added value: +"Geographic region filter, e.g. us, eu, apac, americas"
    • addedInput schema / properties / seller / description
      Added value: +"Filter by selling/target company name, e.g. CyrusOne"
  7. Changed27 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / buyer / default
      Removed value: -""
    • removedInput schema / properties / buyer / title
      Removed value: -"Buyer"
    • removedInput schema / properties / date_from / default
      Removed value: -""
    • removedInput schema / properties / date_from / title
      Removed value: -"Date From"
    • removedInput schema / properties / date_to / default
      Removed value: -""
    • removedInput schema / properties / date_to / title
      Removed value: -"Date To"
    • removedInput schema / properties / deal_type / default
      Removed value: -""
    • removedInput schema / properties / deal_type / title
      Removed value: -"Deal Type"
    • 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 / max_value_usd / default
      Removed value: -0
    • removedInput schema / properties / max_value_usd / title
      Removed value: -"Max Value Usd"
    • removedInput schema / properties / min_value_usd / default
      Removed value: -0
    • removedInput schema / properties / min_value_usd / title
      Removed value: -"Min Value Usd"
    • 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 / region / default
      Removed value: -""
    • removedInput schema / properties / region / title
      Removed value: -"Region"
    • removedInput schema / properties / seller / default
      Removed value: -""
    • removedInput schema / properties / seller / title
      Removed value: -"Seller"
    • removedInput schema / title
      Removed value: -"list_transactionsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_transactionsOutput",
-  "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": "list_transactionsOutput",
+  "type": "object"
+}
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_transactionsOutput",
-  "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": "list_transactionsOutput",
+  "type": "object"
+}
  11. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_transactionsOutput",
-  "type": "object"
-}New value: +null
  12. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond that: deal coverage volume, time range, the caveat that many private deal values are undisclosed, and the exact fields returned. It does not discuss pagination behavior or default ordering, but those are minor for a read-only list tool with an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense yet every sentence earns its place: purpose, return fields, filters, example questions, a concrete try-it example, a common pitfall, and sibling routing. The key scope and exclusion statements are front-loaded near the end but clearly separated, and no sentence is filler.

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 10 parameters, no required fields, and an output schema, the description is complete: it explains domain, scale, temporal range, data caveats, output fields, filterable parameters, example usage, and when to use alternatives. Nothing essential for selecting or invoking the tool is missing; the output schema covers return structure.

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 all 10 parameters. The description adds value by clarifying ISO-8601 date format, giving a concrete min_value_usd example ($1B), showing an example invocation, and explicitly ruling out a `year` parameter. It does not discuss limit/offset/deal_type in prose, but the schema covers those adequately.

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 names a specific verb (list) and resource (M&A and capital transactions in the data center sector), then adds scope details: 2,100+ tracked deals, date range, and return fields. It explicitly distinguishes itself from hyperscaler_deals and deal_autopsy, so an agent can select it correctly without inspecting sibling 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?

It states exactly when to use the tool ('Broad M&A and capital-deal flow with filters') and when not to use it, naming the alternatives: hyperscaler_deals for lease/PPA/JV activity and deal_autopsy for single-deal post-mortems. It also prevents a common mistake by noting there is no `year` parameter and directing the agent to use date_from/date_to.

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