DC Hub

Get Facility Details

get_facility

Read-onlyIdempotent

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). Needs a slug or id from search_facilities. 404 "not found": re-run search_facilities. Gated: give human_url to your human.

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
`data`	No	ONE facility
`quota`	No	Caller quota state (remaining calls, tier).
`_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 lookup executed
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`next_ask`	No	Suggested follow-up
`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.
`_return_loop`	No	Next-session delta call (get_changes).
`preview_is_partial`	No	true when the tier withheld fields
`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

Changed1 schema field changedSep 20, 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 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"
+}

Changed6 schema fields changedJul 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 / description

Added value: +"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 / description

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

addedInput schema / properties / slug / description

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

Changed3 schema fields changedJul 2, 2026

addedInput schema / properties / id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    }
+  ]
+}

addedInput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / slug
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedMay 3, 2026
- addedInput schema / properties / facility_id / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]
```
- removedInput schema / properties / facility_id / type
```
Removed value: -"string"
```

Changed9 schema fields changedApr 29, 2026

addedInput schema / $schema

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

removedInput schema / properties / facility_id / default
```
Removed value: -""
```
removedInput schema / properties / facility_id / title
```
Removed value: -"Facility Id"
```
removedInput schema / properties / include_nearby / default
```
Removed value: -false
```
removedInput schema / properties / include_nearby / title
```
Removed value: -"Include Nearby"
```
removedInput schema / properties / include_power / default
```
Removed value: -false
```
removedInput schema / properties / include_power / title
```
Removed value: -"Include Power"
```
removedInput schema / title
```
Removed value: -"get_facilityArguments"
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_facilityOutput",
-  "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_facilityOutput",
+  "type": "object"
+}

Changed1 schema field changedApr 11, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_facilityOutput",
-  "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_facilityOutput",
+  "type": "object"
+}

Changed1 schema field changedMar 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_facilityOutput",
-  "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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: output cardinality ('Returns ONE facility in full'), gating requirements ('Gated: give human_url to your human'), and 404 handling. It doesn't cover auth scope or rate limits, so it stops short of a 5.

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?

The field enumeration, usage examples, and constraints are all relevant and the 'one facility / do not search' constraint is prominent. The opening field list is long and slightly overloaded, but it is front-loaded and almost every clause earns its 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?

With an output schema present, the description need not explain return values, and it still covers cardinality, the input prerequisite, gating, and error recovery for a 6-parameter lookup tool. Nothing an agent needs to call 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 description coverage is 100%, so the baseline is 3. The description goes further by showing concrete call examples with literal values (id=equinix-dc1-ashburn, slug=digital-realty-iad8) and framing the id/slug/name fallback chain, which clarifies how the anyOf alternatives should be chosen in practice.

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+resource ('Get Facility Details' / 'Full metadata for one facility') and enumerates the returned fields (power capacity, cooling, fiber carriers, DCPI verdict, peers). It explicitly distinguishes itself from the sibling search_facilities by stating it returns ONE facility and must not be used to list many.

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 explicit when-to-use ('Answers "who operates this data center..."'), when-not-to-use (do NOT use to search/list many — use search_facilities), a prerequisite (needs a slug or id from search_facilities), and error recovery (404 → re-run search_facilities). This leaves almost nothing to inference.

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.

Get Facility Details

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources