AIDC AI Design Engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| design | Size an AI data center anywhere in the world. Returns rack count, design PUE, total MVA, and (when available) cost estimate in KRW and timeline in months. Use this when the user asks to dimension, plan, or estimate an AI data center — especially with NVIDIA Hopper, Blackwell, or Vera Rubin (R200) GPUs. From Vera Rubin Ultra onward NVIDIA standardised 800 VDC as the in-rack distribution, so local AC-grid specifics (22.9 kV Korea launch, 11/33 kV EU, 13.8/34.5 kV US, or any MV) reduce to a thin upstream shim — the rack-level design is identical worldwide. |
| validateA | Validate a data center design against engineering rules (electrical, cooling, layout, safety, data). Returns severity-classified findings (blocking | warn | info) and RFI items. Provide EITHER designSummary (previously computed) OR rawInput (engine will size then validate). |
| layout | Generate rack and site layout plans. Returns a rack plan (hall dimensions in mm, row/column grid, per-rack positions and kW) and a site plan (block-level layout in percentage coordinates). Use this AFTER design + validate, when you need the physical layout. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so no possibility of ambiguity. The tool's purpose is clearly defined.
With a single tool, naming consistency is not an issue. The name 'validate' is a clear verb indicating action.
A single tool for a domain like data center design is insufficient. The tool covers validation but omits other essential operations like design creation or modification.
The tool only provides validation, missing CRUD operations for designs, listing, or other lifecycle management. The domain suggests a need for more tools.