Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_chiller_tonnage_cooling

Calculate chilled-water cooling load, refrigeration tons, BTU/hr, thermal kW, and electrical demand from flow rate and entering/leaving water temperatures for commercial HVAC chiller sizing.

Instructions

Commercial HVAC Chiller Tonnage & Cooling Load Calculator. Calculate chilled water cooling capacity in refrigeration tons (TR), kW thermal, and pump flow rate in GPM for commercial HVAC systems. Discipline: ENERGY. Governing mathematical model / formula: Tons of Refrigeration (TR) = (GPM × ΔT in °F) / 24 | 1 TR = 12,000 BTU/hr = 3.517 kW.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of cooling_tonnage (Chiller Cooling Capacity), cooling_btuh (Total Cooling Rate (BTU/hr)), thermal_kw (Thermal Cooling Power), chiller_power_kw (Electrical Input Power Demand) using water_flow_gpm (Chilled Water Flow Rate (GPM) in GPM), entering_water_temp (Entering Water Temp (EWT °F) in °F), leaving_water_temp (Leaving Water Temp (LWT °F) in °F), chiller_kw_per_ton (Chiller Specific Efficiency (kW/Ton) in kW/Ton). 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 'Commercial HVAC Chiller Tonnage & Cooling Load 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): "chiller-tonnage-cooling"

    • category (string): "energy"

    • name (string): "Commercial HVAC Chiller Tonnage & Cooling Load Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.cooling_tonnage (Chiller Cooling Capacity): Formatted display string (e.g. '100.0 Tons (TR)')

      • metrics.cooling_btuh (Total Cooling Rate (BTU/hr)): Formatted display string (e.g. '1,200,000 BTU/hr')

      • metrics.thermal_kw (Thermal Cooling Power): Formatted display string (e.g. '351.7 kW th')

      • metrics.chiller_power_kw (Electrical Input Power Demand): Formatted display string (e.g. '58.0 kW el')

    • 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_chiller_tonnage_cooling"
  }
}

Input Schema

NameRequiredDescriptionDefault
water_flow_gpmNoChilled Water Flow Rate (GPM) (GPM). Gallons per minute circulated through evaporator. Default: 240. Min: 20. Max: 5000.
chiller_kw_per_tonNoChiller Specific Efficiency (kW/Ton) (kW/Ton). Full-load electrical power draw per ton. Default: 0.58. Min: 0.4. Max: 1.2.
leaving_water_tempNoLeaving Water Temp (LWT °F) (°F). Cold chilled supply water temperature. Default: 44. Min: 38. Max: 60.
entering_water_tempNoEntering Water Temp (EWT °F) (°F). Warm return water temperature entering chiller. Default: 54. Min: 45. Max: 85.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description fully carries the burden: it declares the tool read-only, idempotent, stateless, side-effect free, and specifies that out-of-bounds inputs return a diagnostic error rather than throwing. It also documents the complete return envelope and field-by-field metric formatting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Section headers keep it navigable and the purpose is front-loaded, but there is redundant wording such as 'Chilled Water Flow Rate (GPM) in GPM' and label duplication between the 'Discipline' and 'category' fields. The RETURNS block is thorough but long, and the parenthetical unit echoing across every parameter expands length without adding information.

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?

No output schema exists, so the description fully specifies the return structure down to individual metric keys and display formatting. For a four-parameter deterministic calculator, everything an agent needs to call and interpret it is present.

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 coverage is 100%, so all four parameters already carry units, defaults, and min/max bounds in the schema. The description restates the parameter names with units in the WHEN TO USE block but adds little beyond what the schema provides; the formula line implies how inputs combine (GPM × ΔT / 24) but does not clarify parameter-level semantics further.

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 resource and verb ('Commercial HVAC Chiller Tonnage & Cooling Load Calculator'), then names the exact outputs (TR, kW thermal, GPM) and the governing formula. The DISAMBIGUATION section explicitly separates it from omni_universal_query, omni_batch_calculate, and omni_describe_solver.

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?

Provides an explicit WHEN TO USE list mapping each input to each computed metric, an explicit WHEN NOT TO USE clause (no qualitative reasoning, numeric-only inputs), and named alternatives for batch jobs and schema introspection. Nothing about routing is left to inference.

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