DC Hub: Data Center, Power Grid & Energy Intelligence

Plan Fiber Leadin

plan_fiber_leadin

Read-onlyIdempotent

Plan diverse road-following fiber lead-in routes from a data-center site to a carrier hotel/POP, with route lengths, indicative build cost, and corridor-sharing analysis for diversity.

Instructions

Use this when the user asks how to get diverse fiber into a data center site: plans road-following lead-in routes from a candidate data-center site to a carrier hotel / POP, with indicative build cost and a route-diversity read. Answers "can I get N diverse fibre routes into this site, how far, how much, and where do they share a corridor?". Example: plan_fiber_leadin from="250 Paringa Road, Murarrie QLD" to="20 Wharf Street, Brisbane City QLD" n=4. Params: from (lat,lng OR street address), to (lat,lng OR address — e.g. a NextDC/Equinix POP), n (1-6 routes, default 4), fibre ("720F"|"1440F"), bore_m (river/rail bore length in metres, optional). Returns per-route length_km + GeoJSON geometry, total_route_km, diversity {min_separation_m_midhaul, shared_street_km}, and indicative cost {capex_usd, opex_usd_yr}. INDICATIVE auto-routed road corridors — NOT engineered alignments; subject to survey, DBYD and carrier confirmation. Do NOT use for a single site-suitability score (use analyze_site) or fibre-provider footprints (use get_fiber_intel).

Input Schema

Name	Required	Description
`n`	No	Number of diverse routes to plan, 1-6 (default 4)
`to`	Yes	Destination carrier hotel/POP as "lat,lng" OR an address, e.g. "20 Wharf Street, Brisbane City QLD"
`from`	Yes	Origin site as "lat,lng" OR a street address, e.g. "250 Paringa Road, Murarrie QLD"
`fibre`	No	Fibre count spec for cost estimate: "720F" or "1440F"
`bore_m`	No	River/rail bore length in metres to add to the route, 0-100000 (optional)

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

Changed3 schema fields changedAug 30, 2026

removedInput schema / $schema

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

addedInput schema / required
```
Added value: +[
+  "from",
+  "to"
+]
```

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

Changed9 schema fields changedv2.3.6Jul 2, 2026

addedInput schema / properties / bore_m / description

Added value: +"River/rail bore length in metres to add to the route, 0-100000 (optional)"

changedInput schema / properties / bore_m / maximum

Previous value: -9007199254740991New value: +100000

changedInput schema / properties / bore_m / minimum

Previous value: --9007199254740991New value: +0

addedInput schema / properties / fibre / description

Added value: +"Fibre count spec for cost estimate: \"720F\" or \"1440F\""

addedInput schema / properties / from / description

Added value: +"Origin site as \"lat,lng\" OR a street address, e.g. \"250 Paringa Road, Murarrie QLD\""

addedInput schema / properties / n / description

Added value: +"Number of diverse routes to plan, 1-6 (default 4)"

changedInput schema / properties / n / maximum

Previous value: -9007199254740991New value: +6

changedInput schema / properties / n / minimum

Previous value: --9007199254740991New value: +1

addedInput schema / properties / to / description

Added value: +"Destination carrier hotel/POP as \"lat,lng\" OR an address, e.g. \"20 Wharf Street, Brisbane City QLD\""

Addedv2.2.8Jun 17, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description earns credit by adding genuinely non-structured context: routes are 'INDICATIVE auto-routed road corridors — NOT engineered alignments' and are 'subject to survey, DBYD and carrier confirmation,' which sets appropriate expectations about reliability. It stops short of discussing rate limits or latency, so it is not a full 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?

It is a dense but well-ordered block: purpose first, example second, parameter/return summary third, caveats and exclusions last, so it is front-loaded and skimmable. Slightly long for a description, and the inline return-value enumeration borders on redundant given a full output schema, but each sentence carries information.

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 5-parameter, output-schema-backed, annotation-covered tool, the description is complete: it covers trigger, formats, defaults, return shape summary, and the indicative nature of results. An agent has everything needed to select and call it correctly without consulting further docs.

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 would be 3. The description adds value by restating accepted formats with intent ('lat,lng OR street address'), clarifying that 'to' may be a NextDC/Equinix POP, and giving a fully worked example invocation that shows the parameters in combination. That modestly exceeds what the schema alone conveys.

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?

States a specific verb+resource: 'plans road-following lead-in routes from a candidate data-center site to a carrier hotel / POP,' with scope (indicated build cost and route-diversity read). It explicitly distinguishes itself from siblings by naming analyze_site and get_fiber_intel as the wrong tools for adjacent tasks, so an agent can route without opening a schema.

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?

Gives the triggering condition ('when the user asks how to get diverse fiber into a data center site'), a concrete example invocation, and explicit exclusions ('Do NOT use for a single site-suitability score (use analyze_site) or fibre-provider footprints (use get_fiber_intel)'). When-to-use, when-not-to-use, and the named alternatives are all present.

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

Deploy Server