AIDC AI Design Engine

Validate a data center design

validate

Check a design summary or raw input against engineering rules, returning warnings, RFIs, and pending checks; private sessions stay within the signed-in AIDC workflow.

Instructions

Validate a previous design summary or raw design input against engineering rules. Private EngineSessions remain in the signed-in AIDC workflow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rawInput`	No	Raw design request to size and validate.
`designSummary`	No	Previously computed design summary.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.1.2Sep 28, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "designSummary"
+    ]
+  },
+  {
+    "required": [
+      "rawInput"
+    ]
+  }
+]

addedInput schema / description

Added value: +"Provide a previous design summary or raw design input. Private EngineSessions remain in the signed-in AIDC workflow."

removedInput schema / properties / designSummary / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / designSummary / description

Previous value: -"Previously computed design summary. Provide either this OR rawInput."New value: +"Previously computed design summary."

changedInput schema / properties / rawInput / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedInput schema / properties / rawInput / description

Previous value: -"Raw design request. The engine will size first, then validate. Provide either this OR designSummary."New value: +"Raw design request to size and validate."

addedInput schema / properties / rawInput / properties / customInputs

Added value: +{
+  "additionalProperties": {},
+  "description": "Optional project-specific design inputs.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

changedInput schema / properties / rawInput / properties / gpuGen / description

Previous value: -"NVIDIA GPU generation. hopper=H100/H200, blackwell=B100/B200/GB200, rubin=R100/Vera Rubin."New value: +"NVIDIA GPU generation: hopper, blackwell, or rubin."

addedInput schema / properties / rawInput / properties / hallCount

Added value: +{
+  "description": "Optional requested data-hall count.",
+  "exclusiveMinimum": 0,
+  "maximum": 48,
+  "type": "integer"
+}

changedInput schema / properties / rawInput / properties / itLoadMw / description

Previous value: -"IT load in megawatts. 0 < x ≤ 1000."New value: +"IT load in megawatts. 0 < x <= 1000."

removedInput schema / properties / rawInput / properties / options / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / rawInput / properties / options / description

Previous value: -"Optional engineering overrides: redundancy tier (n / n+1 / 2n), cooling mode (air / hybrid / liquid), PUE target (1.0–2.5)."New value: +"Optional redundancy, cooling-mode, and PUE overrides."

addedInput schema / properties / rawInput / properties / parcels

Added value: +{
+  "description": "Optional bounded GeoJSON parcel features.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "geometry": {
+        "anyOf": [
+          {
+            "properties": {
+              "coordinates": {
+                "items": {
+                  "items": {
+                    "items": {
+                      "type": "number"
+                    },
+                    "maxItems": 3,
+                    "minItems": 2,
+                    "type": "array"
+                  },
+                  "maxItems": 512,
+                  "minItems": 4,
+                  "type": "array"
+                },
+                "maxItems": 16,
+                "minItems": 1,
+                "type": "array"
+              },
+              "type": {
+                "const": "Polygon",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "coordinates"
+            ],
+            "type": "object"
+          },
+          {
+            "properties": {
+              "coordinates": {
+                "items": {
+                  "items": {
+                    "items": {
+                      "items": {
+                        "type": "number"
+                      },
+                      "maxItems": 3,
+                      "minItems": 2,
+                      "type": "array"
+                    },
+                    "maxItems": 512,
+                    "minItems": 4,
+                    "type": "array"
+                  },
+                  "maxItems": 16,
+                  "minItems": 1,
+                  "type": "array"
+                },
+                "maxItems": 8,
+                "minItems": 1,
+                "type": "array"
+              },
+              "type": {
+                "const": "MultiPolygon",
+                "type": "string"
+              }
+            },
+            "required": [
+              "type",
+              "coordinates"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      "id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          }
+        ]
+      },
+      "properties": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": {
+        "const": "Feature",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "geometry"
+    ],
+    "type": "object"
+  },
+  "maxItems": 25,
+  "type": "array"
+}

changedInput schema / properties / rawInput / properties / rackDensityKw / description

Previous value: -"Per-rack power in kW. 0 < x ≤ 500. Rubin Ultra targets 300+."New value: +"Requested per-rack power in kW. 0 < x <= 500."

changedInput schema / properties / rawInput / properties / region / description

Previous value: -"Site classification. metropolitan = dense urban / capital region (e.g. Seoul / Tokyo / Frankfurt / Northern Virginia), regional = secondary / suburban / industrial-park region. Drives utility cost and substation availability assumptions."New value: +"Metropolitan or regional site class."

changedInput schema / properties / rawInput / properties / siteAreaSqm / description

Previous value: -"Total site area in m². 0 < x ≤ 1,000,000."New value: +"Total site area in square meters."

Addedv0.1.1Jul 25, 2026
RemovedJul 25, 2026
First observedv0.1.0Jul 13, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Against engineering rules' is vague about what is checked or returned, and the EngineSessions sentence only hints at session/auth scoping ('signed-in AIDC workflow') without stating whether validation mutates state or requires authentication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and tight, which is good. The second sentence about private EngineSessions is cryptic and its contribution is unclear, so it does not clearly earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex validation tool with deep nested schemas, no annotations, and no output schema, yet the description never explains what a validation result looks like or what happens on failure. Given the complexity, the description leaves significant gaps for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 correctly names the two mutually exclusive inputs matching the schema's anyOf, but adds no syntax, format, or constraint detail beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (validate) and resource (data center design) and clarifies the two accepted input forms (design summary or raw input). It does not differentiate itself from the sibling tools 'design' and 'layout', so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Validate a previous design summary or raw design input' implies the follow-on role after a design step, which is useful. However, there is no explicit when-not guidance and no routing to the 'design' or 'layout' siblings, leaving the agent to infer which tool starts the workflow.

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

Deploy Server

Validate a data center design

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools