dcfg-mcp
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.
Field calculations for data center engineering: liquid-cooling loop hydraulics, SOP/MOP/EOP classification, and ANSI/ISA-71.04 corrosion coupon classification. Results are design estimates and screening checks, not acceptance records.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| liquid_loop_hydraulicsA | Size a liquid-cooling loop (for example an NVL72 rack or a liquid load bank). Computes the required coolant flow from heat load and Delta-T (Q = m_dot * cp * dT), the mean velocity in the pipe, and the pressure drop from pipe friction, local loss coefficients (zeta) and quick-disconnect couplings (from published Cv values). coolant: "water" or "pg25" (25 % propylene glycol), or pass your own density, specific heat and viscosity. Flags velocities above the 3.0 m/s field guideline. |
| classify_procedureA | Classify a data center task as SOP, MOP or EOP and list what the paper is missing. EOP: a service or person is in danger now; it stops at the first safe state. MOP: the work changes redundancy or switching topology; it needs a Point of No Return, a back-out plan and approval before work. SOP: a repeatable routine that never changes redundancy. A Permit to Work is an administrative gate, not a fourth procedure. |
| classify_corrosion_couponA | Classify a corrosion coupon result under ANSI/ISA-71.04-2013 (G1/G2/G3/GX). Normalises the measured film thickness to 30 days (R30 = X * 30 / T), classifies copper and silver separately, and reports the room class as the worse of the two. A copper-only result cannot prove G1. Field blanks are reported but never subtracted. |
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 address completely different artifacts: a hydraulic sizing calculation, procedure classification (SOP/MOP/EOP), and corrosion coupon classification per ANSI/ISA-71.04. There is no plausible overlap in intent, so an agent cannot reasonably misselect among them.
All names use consistent snake_case and are descriptive, but the convention is mixed: classify_procedure and classify_corrosion_coupon follow a verb_noun pattern while liquid_loop_hydraulics is a bare noun phrase. The deviation is minor and the topic words still disambiguate clearly.
Three tools is on the thin side, but each is a substantive, self-contained engineering calculation with real internal logic (pressure drop, R30 normalisation, procedure gap analysis) rather than a thin wrapper. Nothing feels padded or redundant.
Each tool fully closes its own loop (inputs, computation, classification output, and caveats like velocity flags and bl-than-G1 warnings), so no dead ends within a task. As a broader data-center facilities surface it is narrow — no airflow/power/electrical or unit-conversion helpers, and no way to carry coupon results across time — but those are scope choices, not broken workflows.