AIDC AI Design Engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIDC_API_KEY | Yes | Registered AIDC integration key required for calculations. |
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 |
|---|---|
| designC | Generate a profile-aware AI data center design basis from OPR inputs and optional project data. |
| validateB | Validate a previous design summary or raw design input against engineering rules. Private EngineSessions remain in the signed-in AIDC workflow. |
| layoutC | Generate profile-aware physical rack blocks, rack-plan candidates, and site layout data from a nested design request. |
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 3 tools
The three tools target distinct stages: design generates the design basis, validate checks inputs/rules, layout produces physical rack/site data. No functional overlap; boundaries are clear from descriptions.
All tool names are single, lowercase action words (design, validate, layout) following a consistent terse style. No mixed conventions or casing.
Three tools is well within the ideal 3-15 range and each maps to a core operation (generate, validate, layout). No redundant tools; the set is tightly scoped.
Core generate-validate-layout pipeline is covered, but there is no explicit retrieval/update/list for designs, and sessions are handled externally. Minor gaps may require workarounds but no critical dead end.