DC Hub Intelligence

Get Facility Details

get_facility

Read-onlyIdempotent

Retrieve one facility's full profile: operator, address, power, cooling, fiber carriers, and nearby peers — to answer who operates the data center and how many carriers are on-site.

Instructions

Full metadata for one facility — name, operator, address, lat/lon, power capacity (MW total/used), cooling type, fiber providers (count + carrier list), commissioning year, status, the DCPI verdict for its market, and peer facilities nearby. Answers "who operates this data center and how big is it", "how many fiber carriers are in that building". Try: get_facility id=equinix-dc1-ashburn — or get_facility slug=digital-realty-iad8. Returns ONE facility in full; do NOT use to search or list many facilities (use search_facilities).

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Alias for facility_id — a facility id/slug from a prior search result
`name`	No	Facility name as a fallback lookup when no id/slug is known, e.g. "QTS Ashburn"
`slug`	No	Facility slug from a prior search result, e.g. digital-realty-iad8
`facility_id`	No	Facility id from a prior search_facilities/search result (numeric or string), e.g. equinix-dc1-ashburn
`include_power`	No	Include power capacity detail (total/used MW) in the response (default true)
`include_nearby`	No	Include peer facilities near this one in the response (default true)

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier) when available.
`_entity`	No	Payload class discriminator (e.g. facility\|market\|iso_grid\|queue_results\|deal\|report\|response) — branch on this before parsing the rest.
`citation`	No	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.
`provenance`	No	Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing.
`_front_door`	No	In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan.
`_return_loop`	No	Suggested next-session delta call (get_changes since=24h) so you pull only what changed.
`site_evaluation_handoff`	No	Pre-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.

Changed1 schema field changedv2.12.20Sep 26, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "facility_id": {}
+    },
+    "required": [
+      "facility_id"
+    ]
+  },
+  {
+    "properties": {
+      "id": {}
+    },
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "properties": {
+      "slug": {}
+    },
+    "required": [
+      "slug"
+    ]
+  },
+  {
+    "properties": {
+      "name": {}
+    },
+    "required": [
+      "name"
+    ]
+  }
+]

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

Changed6 schema fields changedv2.3.6Jul 2, 2026

addedInput schema / properties / facility_id / description

Added value: +"Facility id from a prior search_facilities/search result (numeric or string), e.g. equinix-dc1-ashburn"

addedInput schema / properties / id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ],
+  "description": "Alias for facility_id — a facility id/slug from a prior search result"
+}

addedInput schema / properties / include_nearby / description

Added value: +"Include peer facilities near this one in the response (default true)"

addedInput schema / properties / include_power / description

Added value: +"Include power capacity detail (total/used MW) in the response (default true)"

addedInput schema / properties / name

Added value: +{
+  "description": "Facility name as a fallback lookup when no id/slug is known, e.g. \"QTS Ashburn\"",
+  "type": "string"
+}

addedInput schema / properties / slug

Added value: +{
+  "description": "Facility slug from a prior search result, e.g. digital-realty-iad8",
+  "type": "string"
+}

First observedv2.1.19Jun 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish this is read-only, idempotent, and non-destructive. The description adds the key behavioral nuance that exactly one facility is returned and that nearby peers are bundled into the response, plus a clear exclusion of bulk listing. This goes beyond the annotations without contradicting them.

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 front-loaded with the core scope, then gives field detail, example calls, and an explicit boundary warning. Each sentence earns its place, and the final 'use search_facilities' note is concise and actionable.

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?

Given the read-only annotations, 100% schema description coverage, and the presence of an output schema, the description is complete. It covers what the tool does, how to invoke it with realistic examples, what it returns, and when not to use it.

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?

The schema covers all parameters with descriptions, so the baseline is 3. The description adds value with concrete example identifiers (id=equinix-dc1-ashburn, slug=digital-realty-iad8) and clarifies that lookups can be done by id, slug, or name, which helps an agent map real-world tokens to the schema fields.

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 clearly states the tool retrieves full metadata for one facility and enumerates the returned fields (name, operator, address, power, cooling, fiber, etc.). It explicitly distinguishes this from search_facilities by saying it returns ONE facility and should not be used to search or list many facilities.

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?

The description provides direct usage context: it answers specific questions like 'who operates this data center' and 'how many fiber carriers are in that building'. It also gives explicit negative guidance ('do NOT use to search or list many facilities') and names the alternative tool, search_facilities.

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

Deploy Server