DC Hub

Feeder Hosting Capacity

get_hosting_capacity

Read-onlyIdempotent

Utility-PUBLISHED feeder hosting capacity — the MW a NAMED distribution feeder can actually take, straight from the utility's own hosting-capacity GIS. Published records from many utilities (e.g. Con Edison, National Grid NY/MA, NYSEG/RG&E, Rhode Island Energy, Orange & Rockland, Central Hudson, Eversource CT, BGE, Pepco/Delmarva/ACE, Dominion VA, Ameren Illinois, AEP Ohio & I&M, Xcel MN/CO, DTE, Avista; the no-args call lists current coverage). This is filed distribution-level truth, not a proximity proxy. Three ways to call it: lat+lon (+radius_km, default 25) for a point; utility or market for a whole published territory; NO ARGS for the coverage list of every market that has data. CRITICAL — check capacity_type before quoting any number: "load" = LOAD-serving headroom, what a new data-center load can actually DRAW (only Ameren Illinois, AEP Ohio & I&M and Central Hudson publish it); "gen" = DER/generation EXPORT capacity, what the feeder can ACCEPT from solar/storage — it is NOT available load and must never be relayed as "you can site N MW here"; "bus_headroom" = transmission bus MW. Returns, split by capacity_type: distinct feeder count, max + median MW, the top feeders with voltage_kv, feeder_id, coords and publish date (the utility substation label needs a paid DC Hub plan), plus the utilities publishing them. Honest by construction — published rows are GIS vertices, so distinct_feeders and geometry_rows_scanned are reported separately (never conflated), and a capacity-capped read is flagged sample_complete=false with the capacity_floor_mw at or above which the set IS provably complete. Coverage is concentrated in the Northeast, Mid-Atlantic and Midwest — NOT nationwide — and a point outside them returns an explicit not-published answer with the nearest covered markets, never a silent zero. Answers "can this feeder actually take 20 MW", "where can I plug in without waiting on a substation upgrade". Try: get_hosting_capacity utility="Ameren Illinois" capacity_type=load min_mw=5. Do NOT use for transmission-substation proximity or time-to-power (use get_grid_intelligence), the ISO interconnection queue (use get_interconnection_queue / get_refined_queue), or retiring-plant headroom (use get_retirement_headroom) — this is the distribution FEEDER layer. Informational, not binding interconnection guidance; verify with the utility.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude of the point to search around, decimal degrees. Must be paired with lon.
`lng`	No	Alias for lon — either name works
`lon`	No	Longitude of the point to search around, decimal degrees. Must be paired with lat.
`limit`	No	Max results to return (1-500; default varies by tool)
`market`	No	Alias for utility — either name works (e.g. "Northern Virginia · Richmond", "New York City · Westchester").
`min_mw`	No	Only return feeders whose published capacity is at or above this many MW.
`utility`	No	Utility or market name, case-insensitive substring — e.g. "Ameren Illinois", "Con Edison", "Providence". Searches that utility's whole published territory instead of a point radius. Call with NO arguments to list every covered utility.
`latitude`	No	Alias for lat — either name works
`longitude`	No	Alias for lon — either name works
`radius_km`	No	Search radius in km around lat/lon (default 25, max 150). Ignored when utility/market is passed — that mode covers the utility's entire published extent.
`capacity_type`	No	Restrict to one published type: "load" (what a new data-center load can DRAW — the type that answers siting), "gen" (DER/generation EXPORT headroom — NOT available load), or "bus_headroom" (transmission bus MW). Omit to get all three reported separately.

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	No	Caller quota state (remaining calls, tier).
`_entity`	No	Payload class (facility\|market\|iso_grid\|queue_results\|deal\|report\|response); branch on it.
`citation`	No	How to attribute DC Hub: {source, url, license, cite_as, retrieved_at}, or the attribution line as a string.
`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).
`site_evaluation_handoff`	No	Follow-up calls [{tool, parameters, why}] when the payload carries coordinates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "description": "DC Hub envelope: tool data fields ride at the top level beside these keys.",
+  "properties": {
+    "_entity": {
+      "description": "Payload class (facility|market|iso_grid|queue_results|deal|report|response); branch on it.",
+      "type": "string"
+    },
+    "_front_door": {
+      "additionalProperties": {},
+      "description": "First-tool hint: plan_query(intent) returns the ordered plan.",
+      "properties": {},
+      "type": "object"
+    },
+    "_return_loop": {
+      "additionalProperties": {},
+      "description": "Next-session delta call (get_changes).",
+      "properties": {},
+      "type": "object"
+    },
+    "citation": {
+      "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."
+    },
+    "provenance": {
+      "additionalProperties": {},
+      "description": "Source, method, as_of, verification_counts, license, cite_as; quote it when citing.",
+      "properties": {},
+      "type": "object"
+    },
+    "quota": {
+      "additionalProperties": {},
+      "description": "Caller quota state (remaining calls, tier).",
+      "properties": {},
+      "type": "object"
+    },
+    "site_evaluation_handoff": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "properties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {},
+          "properties": {},
+          "type": "object"
+        }
+      ],
+      "description": "Follow-up calls [{tool, parameters, why}] when the payload carries coordinates."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -{
-  "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": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {},
-          "type": "object"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "description": "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": {
-      "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"
-}New value: +null

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

AddedJul 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare a safe read (readOnlyHint=true, idempotentHint=true, destructiveHint=false), and the description adds substantial behavioral context beyond them: the load vs gen vs bus_headroom semantic trap, the sample_complete=false / capacity_floor_mw completeness flag, the distinct_feeders vs geometry_rows_scanned honesty distinction, the concentrated (not nationwide) coverage, and the explicit not-published answer instead of a silent zero.

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 is long (~400 words) and repeats a few schema facts (aliases, radius default), but it is densely front-loaded with the core statement and every section earns its place given the many sibling tools it must disambiguate. Slightly verbose rather than wasteful.

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?

Despite an output schema existing (so return values needn't be restated), the description adds the coverage caveats, edge-case behavior, capacity_type pitfalls, and call modes that an agent needs to use an 11-parameter, multi-mode tool correctly. Nothing material 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, and the schema already documents aliases, defaults, and ranges. The description adds genuine interpretive value by stating which capacity_type answers siting ('load'), which must never be relayed as available load ('gen'), and the default radius and territory-wide behavior of utility/market, going 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 first sentence names the exact resource and scope: 'Utility-PUBLISHED feeder hosting capacity — the MW a NAMED distribution feeder can actually take.' It explicitly contrasts itself with 'a proximity proxy' and later with get_grid_intelligence, get_interconnection_queue, and get_retirement_headroom, so an agent can distinguish it from siblings 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 enumerates the three call modes (lat/lon+radius, utility/market, no-args) with conditions, warns to check capacity_type before quoting, and gives explicit when-not-to-use guidance pointing to named alternatives for transmission proximity, interconnection queue, and retirement headroom. Nothing is left 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.