Skip to main content
Glama
dcfg-mcp

dcfg-mcp

liquid_loop_hydraulics

Size liquid-cooling loops by calculating coolant flow from heat load and Delta-T, pipe velocity, and pressure drop from friction, fittings, and quick-disconnect couplings; flags >3.0 m/s.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "heat_kw": "<heat_kw>",
      "delta_t_k": "<delta_t_k>",
      "pipe_inner_diameter_mm": "<pipe_inner_diameter_mm>"
    },
    "name": "liquid_loop_hydraulics"
  }
}

Input Schema

NameRequiredDescriptionDefault
coolantNopg25
heat_kwYes
delta_t_kYes
coupling_cvNo
density_kg_m3No
pipe_length_mNo
viscosity_pa_sNo
pipe_roughness_mmNo
specific_heat_kj_kgkNo
pipe_inner_diameter_mmYes
sum_local_loss_coefficientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does well to disclose the computation model and that it flags velocities above the 3.0 m/s field guideline, and it states which coolants are supported. It says nothing about the shape or units of the computed results, whether pressure drop includes both major and minor losses in one figure, or how invalid inputs (e.g., zero delta-T) are handled.

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?

Front-loaded with purpose and use cases, then the physics, then the coolant options and the velocity warning. It is compact for an 11-parameter engineering tool, with no filler sentences, though the formula parenthetical is more pedagogical than operational.

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

Completeness3/5

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

For an 11-parameter calculation tool with no annotations, no output schema, and zero schema descriptions, the definition covers purpose and method but leaves output format, units, and override precedence unexplained. An agent could call it, but not reliably interpret or populate the optional fluid-property parameters without guessing.

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 0%, so the description must compensate; it does so partially by explaining that coolant is 'water' or 'pg25' or that you can supply your own density, specific heat and viscosity, and by naming the physics roles of heat load, delta-T, diameter, friction, zeta and Cv. Units are never stated for any parameter (heat_kw, delta_t_k, pipe_inner_diameter_mm are only implied by key names), and it does not clarify that custom fluid properties override the coolant preset or that coupling_cv is a list.

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?

Opens with a specific verb and resource ('Size a liquid-cooling loop') and names concrete use cases (NVL72 rack, liquid load bank). It goes on to enumerate exactly which quantities it computes — flow from Q = m_dot*cp*dT, mean velocity, and pressure drop from friction, zeta coefficients, and quick-disconnect Cv — so an agent knows precisely what the tool returns conceptually.

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?

Usage is implied by the sizing examples, but there is no explicit statement of when to use this versus anything else, no prerequisites, and no mention of when it is inappropriate. The named siblings (classify_corrosion_coupon, classify_procedure) are different domains, so no routing guidance is strictly needed, but the description still leaves the agent to infer context.

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