DC Hub: Data Center, Power Grid & Energy Intelligence

Nearby Infrastructure

get_infrastructure

Read-onlyIdempotent

Find nearby power infrastructure for a site—substations, transmission lines, gas pipelines, and power plants within a configurable radius—with distance and capacity details.

Instructions

Use this when the user asks what power infrastructure is near a site: substations (count + max voltage_kv within radius), transmission lines (>69 kV path overlay), interstate + lateral gas pipelines, and power plants (operating + planned, by fuel) within configurable radius_km. Returns distance + capacity for each, joined to HIFLD/EIA. Answers "what is near this parcel", "how far is the nearest substation and what voltage is it". Try: get_infrastructure lat=33.45 lon=-112.07 radius_km=25. Returns raw nearby assets; do NOT use for a single scored site-suitability verdict (use analyze_site).

Input Schema

Name	Required	Description
`lat`	No	Center latitude in decimal degrees (-90 to 90, required), e.g. 33.45
`lng`	No	Alias for lon — either name works
`lon`	No	Center longitude in decimal degrees (-180 to 180, required), e.g. -112.07
`layer`	No	Optional single asset layer to return, e.g. substations, transmission, pipelines, power_plants
`limit`	No	Max results to return (1-500; default varies by tool)
`latitude`	No	Alias for lat — either name works
`longitude`	No	Alias for lon — either name works
`radius_km`	No	Search radius in kilometers around the point, e.g. 25
`min_voltage_kv`	No	Only include transmission/substations at or above this voltage in kV, e.g. 69

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.12.45Oct 22, 2026

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```

removedOutput schema / description

Removed value: -"DC Hub envelope: tool data fields ride at the top level beside these keys."

removedOutput schema / properties / _entity

Removed value: -{
-  "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
-  "type": "string"
-}

removedOutput schema / properties / _front_door

Removed value: -{
-  "additionalProperties": {},
-  "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / _return_loop

Removed value: -{
-  "additionalProperties": {},
-  "description": "Next-session delta call (get_changes).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / citation

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    },
-    {
-      "type": "string"
-    }
-  ],
-  "description": "How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."
-}

removedOutput schema / properties / provenance

Removed value: -{
-  "additionalProperties": {},
-  "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / quota

Removed value: -{
-  "additionalProperties": {},
-  "description": "Caller quota state (remaining calls, tier).",
-  "properties": {},
-  "type": "object"
-}

removedOutput schema / properties / site_evaluation_handoff

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": {},
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "additionalProperties": {},
-      "properties": {},
-      "type": "object"
-    }
-  ],
-  "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
-}

Changed8 schema fields changedv2.12.43Oct 15, 2026

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: +"DC Hub envelope: tool data fields ride at the top level beside these keys."

changedOutput schema / properties / _entity / description

Previous value: -"Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest."New value: +"Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it."

changedOutput schema / properties / _front_door / description

Previous value: -"In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan."New value: +"First-tool hint: plan_query(intent) returns the ordered plan."

changedOutput schema / properties / _return_loop / description

Previous value: -"Suggested next-session delta call (get_changes since=24h) so you pull only what changed."New value: +"Next-session delta call (get_changes)."

changedOutput schema / properties / citation / description

Previous 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."New value: +"How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string."

changedOutput schema / properties / provenance / description

Previous value: -"Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing."New value: +"Source, method, as_of, verification_counts, license, cite_as; quote it when citing."

changedOutput schema / properties / quota / description

Previous value: -"Caller quota state (remaining calls, tier) when available."New value: +"Caller quota state (remaining calls, tier)."

changedOutput schema / properties / site_evaluation_handoff / description

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

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"
```

Changed4 schema fields changedv2.3.12Jul 28, 2026

addedInput schema / properties / latitude

Added value: +{
+  "description": "Alias for lat — either name works",
+  "type": "number"
+}

addedInput schema / properties / lng

Added value: +{
+  "description": "Alias for lon — either name works",
+  "type": "number"
+}

addedInput schema / properties / longitude

Added value: +{
+  "description": "Alias for lon — either name works",
+  "type": "number"
+}

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

Changed8 schema fields changedv2.3.6Jul 2, 2026

addedInput schema / properties / lat / description

Added value: +"Center latitude in decimal degrees (-90 to 90, required), e.g. 33.45"

addedInput schema / properties / layer / description

Added value: +"Optional single asset layer to return, e.g. substations, transmission, pipelines, power_plants"

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 / lon / description

Added value: +"Center longitude in decimal degrees (-180 to 180, required), e.g. -112.07"

addedInput schema / properties / min_voltage_kv / description

Added value: +"Only include transmission/substations at or above this voltage in kV, e.g. 69"

addedInput schema / properties / radius_km / description

Added value: +"Search radius in kilometers around the point, e.g. 25"

First observedv2.1.19Jun 8, 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, idempotentHint, and non-destructive behavior, so the safety profile is covered structurally. The description adds meaningful context beyond that: the upstream data sources (HIFLD/EIA), that results are 'raw nearby assets' rather than scored output, and that each asset carries distance and capacity. It does not discuss pagination or rate limits, but with strong annotation coverage that gap is minor.

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 description is dense and front-loads the core purpose before enumerating layers and the exclusion. Every sentence carries information, though the listing of layers plus data sources plus sample query makes it slightly long; nothing is wasted but it is near the upper practical length.

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?

An output schema exists, so return-value documentation is not required, yet the description still summarizes the shape (distance + capacity per asset). With 9 params fully covered by the schema, annotations handling safety, and an explicit sibling exclusion, nothing an agent needs to invoke this 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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema alone doesn't convey: layer values map to distinct asset types (substations/transmission/pipelines/power_plants), transmission is filtered at >69 kV, and power plants are split into operating + planned by fuel. The worked example (lat/lon/radius_km) also demonstrates intended usage beyond the field docs.

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 gives a specific verb and resource ('what power infrastructure is near a site') and enumerates exactly what is returned: substations with count and max voltage, transmission lines over 69 kV, pipelines, and power plants by fuel. It explicitly distinguishes itself from the sibling analyze_site, 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?

It states when to use it ('when the user asks what power infrastructure is near a site'), supplies sample utterances that trigger it, and names the exclusion: 'do NOT use for a single scored site-suitability verdict (use analyze_site).' Both the trigger and the anti-trigger are present with the alternative named.

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

Deploy Server