Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_darcy_weisbach_head_loss

Calculate Darcy-Weisbach pipe friction head loss, pressure drop, flow velocity, and Reynolds flow regime from flow rate, diameter, length, and friction factor to verify pressurized pipe performance.

Instructions

Darcy-Weisbach Pipe Friction Head Loss & Pressure Drop Calculator. Calculate friction head loss (h_f in feet), pressure drop (psi), and Reynolds number (laminar vs turbulent) for pressurized fluid flow in commercial pipe networks. Discipline: ENGINEERING. Governing mathematical model / formula: Head Loss h_f = f · (L / D) · (v² / [2 · g]) | Pressure Drop ΔP = h_f · ρ · g / 144.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of friction_head_loss_feet (Total Friction Head Loss), pressure_drop_psi (Total Pressure Drop across Run), fluid_flow_velocity_fps (Mean Flow Velocity), reynolds_flow_regime (Reynolds Number Flow Regime) using pipe_inside_diameter_in (Pipe Inside Diameter (Inches) in in), pipe_length_feet (Total Pipe Run Length (Feet) in ft), flow_rate_gpm (Volumetric Flow Rate (GPM) in GPM), darcy_friction_factor (Darcy Friction Factor (f)). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Darcy-Weisbach Pipe Friction Head Loss & Pressure Drop Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "darcy-weisbach-head-loss"

    • category (string): "engineering"

    • name (string): "Darcy-Weisbach Pipe Friction Head Loss & Pressure Drop Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.friction_head_loss_feet (Total Friction Head Loss): Formatted display string (e.g. '14.28 ft H₂O')

      • metrics.pressure_drop_psi (Total Pressure Drop across Run): Formatted display string (e.g. '6.18 PSI Drop')

      • metrics.fluid_flow_velocity_fps (Mean Flow Velocity): Formatted display string (e.g. '7.23 ft / second')

      • metrics.reynolds_flow_regime (Reynolds Number Flow Regime): Formatted display string (e.g. 'Turbulent (Re ≈ 3.7 × 10⁵)')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_darcy_weisbach_head_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_rate_gpmNoVolumetric Flow Rate (GPM) (GPM). Water flow rate through pipe. Default: 650. Min: 5. Max: 15000.
pipe_length_feetNoTotal Pipe Run Length (Feet) (ft). Length of straight pipe run. Default: 500. Min: 10. Max: 50000.
darcy_friction_factorNoDarcy Friction Factor (f). Moody chart value (commercial steel water pipe typically 0.018 - 0.022). Default: 0.019. Min: 0.008. Max: 0.08.
pipe_inside_diameter_inNoPipe Inside Diameter (Inches) (in). Nominal 6-inch Schedule 40 Steel = 6.065 inches ID. Default: 6.065. Min: 0.5. Max: 72.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so thoroughly: it declares deterministic floating-point computation, read-only/idempotent/stateless behavior, zero side effects, input validation against bounds, and safe diagnostic error returns. It also describes the structured response and gives example formatted metric outputs.

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?

The definition is long but well structured into purpose, usage, disambiguation, behavior, and returns, with useful information front-loaded. Some repetition of parameter labels and units makes it slightly less concise than it could be.

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

Completeness5/5

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

Although no output schema is present, the description fully documents the response shape, computed metrics, status handling, and validation behavior. For a deterministic four-parameter calculator, an agent has everything needed to select and invoke 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 schema already documents all four parameters, their units, ranges, defaults, and physical meaning. The description restates parameter names and units but adds little semantic detail beyond the schema, so a baseline score of 3 is appropriate.

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?

The description states a specific calculator name and clearly defines the calculation: Darcy-Weisbach pipe friction head loss, pressure drop, flow velocity, and Reynolds regime. It distinguishes itself from generic dispatchers and names the sibling tools to use for batch jobs or schema inspection.

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

Usage Guidelines5/5

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

It gives explicit WHEN TO USE and WHEN NOT TO USE guidance, including the exact output metrics computed and the requirement that all inputs be valid numerical values. It also names concrete alternatives for multi-calculation jobs and schema inspection.

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

Deploy Server

Other Tools