Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_tankless_water_heater

Calculate required GPM, temperature rise, and gas or electric heating capacity to size tankless water heaters from simultaneous showers, sinks, and appliances.

Instructions

Tankless Water Heater GPM & Sizing Calculator. Calculate required Gallons Per Minute (GPM), incoming ground water temperature rise (ΔT), and heating capacity for on-demand water heaters. Discipline: CONSTRUCTION. Governing mathematical model / formula: Required GPM = Sum of Concurrent Fixture Flow Rates.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of peak_gpm (Peak Flow Demand (GPM)), temp_rise (Required Temperature Rise (ΔT)), gas_btu_input (Natural Gas Input Required), electric_kw_draw (Electric Equivalent Draw) using showers (Simultaneous Showers Running), sinks (Simultaneous Sinks / Faucets), appliances (Dishwasher or Washing Machine), inlet_temp (Incoming Ground Water Temp in °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 'Tankless Water Heater GPM & Sizing 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): "tankless-water-heater"

    • category (string): "construction"

    • name (string): "Tankless Water Heater GPM & Sizing Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.peak_gpm (Peak Flow Demand (GPM)): Formatted display string (e.g. '7.5 GPM')

      • metrics.temp_rise (Required Temperature Rise (ΔT)): Formatted display string (e.g. '70°F Rise (to 120°F)')

      • metrics.gas_btu_input (Natural Gas Input Required): Formatted display string (e.g. '199,000 BTU/hr')

      • metrics.electric_kw_draw (Electric Equivalent Draw): Formatted display string (e.g. '36 kW (150 Amps)')

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

Input Schema

NameRequiredDescriptionDefault
sinksNoSimultaneous Sinks / Faucets. Bathroom/kitchen sink consumes 1.0 to 1.5 GPM. Default: 2. Min: 0. Max: 6.
showersNoSimultaneous Showers Running. Standard shower consumes 2.0 to 2.5 GPM. Default: 2. Min: 0. Max: 5.
appliancesNoDishwasher or Washing Machine. Consumes ~1.5 to 2.0 GPM. Default: 1. Min: 0. Max: 3.
inlet_tempNoIncoming Ground Water Temp (°F). 35-45°F in North; 60-70°F in Deep South. Default: 50. Min: 35. Max: 75.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of it: declares the tool read-only, idempotent, and stateless with zero side effects, and states that out-of-bounds arguments return a safe diagnostic error rather than throwing. The only gaps are operational details such as latency or unit-handling edge cases beyond the bounds already in the schema.

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?

Well structured with labeled sections (usage, disambiguation, behavior, returns) and the purpose front-loaded in the first two lines. Some redundancy exists, notably the RETURNS block re-listing field names that mirror the inputs and metrics labels, but since no output schema exists this detail is largely justified.

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 must describe returns, and it does so thoroughly with field-by-field types and example formatted values. Combined with the stated formula, input validation behavior, and sibling routing, 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% and each parameter already documents meaning, units, defaults, and min/max. The description restates the parameter roles in the WHEN TO USE line but adds little beyond the schema, so the baseline of 3 applies.

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?

States a specific verb-and-resource pair: calculates required GPM, temperature rise, and heating capacity for on-demand tankless water heaters, plus the underlying model ('Required GPM = Sum of Concurrent Fixture Flow Rates'). It also explicitly distinguishes itself from the generic dispatcher omni_universal_query and from omni_batch_calculate.

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 block naming the computed outputs and the four inputs, a WHEN NOT TO USE block (no qualitative reasoning, all inputs must be numeric), and DISAMBIGUATION routing to omni_batch_calculate for chained jobs and omni_describe_solver for 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