Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_vfd_pump_savings

Calculate VFD energy savings, power draw reduction, and payback for centrifugal pumps using Affinity Laws. Enter motor size, average speed, run hours, and installed cost.

Instructions

Variable Frequency Drive (VFD) Pump Affinity Law Savings Calculator. Calculate electrical energy savings and payback from installing a Variable Frequency Drive (VFD / VSD) on centrifugal pumps and fans using Affinity Laws. Discipline: ENERGY. Governing mathematical model / formula: Power P₂ = P₁ · (RPM₂ / RPM₁)³ | Power scales with the CUBE of speed.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of annual_dollar_savings (Annual Electric Cost Savings), payback_timeline (Simple Payback Period), power_draw_reduction (Power Consumption Reduction), reduced_kw_draw (New Operating Power Draw) using motor_nameplate_hp (Pump Motor Size (HP) in HP), average_speed_pct (Average Reduced Operating Speed (%) in %), annual_running_hours (Annual Operating Hours in hrs/yr), vfd_installed_cost (VFD Turnkey Installed Cost ($)). 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 'Variable Frequency Drive (VFD) Pump Affinity Law Savings 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): "vfd-pump-savings"

    • category (string): "energy"

    • name (string): "Variable Frequency Drive (VFD) Pump Affinity Law Savings Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.annual_dollar_savings (Annual Electric Cost Savings): Formatted display string (e.g. '$10,720.00')

      • metrics.payback_timeline (Simple Payback Period): Formatted display string (e.g. '8.4 months')

      • metrics.power_draw_reduction (Power Consumption Reduction): Formatted display string (e.g. '48.8% Saved')

      • metrics.reduced_kw_draw (New Operating Power Draw): Formatted display string (e.g. '20.9 kW (vs 40.8 kW full)')

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

Input Schema

NameRequiredDescriptionDefault
average_speed_pctNoAverage Reduced Operating Speed (%) (%). Average flow/speed requirement (e.g. 80% speed meets 80% flow). Default: 80. Min: 40. Max: 95.
motor_nameplate_hpNoPump Motor Size (HP) (HP). Rated nameplate mechanical horsepower. Default: 50. Min: 5. Max: 500.
vfd_installed_costNoVFD Turnkey Installed Cost ($). Drive purchase, line reactor, enclosure, and wiring. Default: 7500. Min: 1500. Max: 75000.
annual_running_hoursNoAnnual Operating Hours (hrs/yr). Pump run hours per year. Default: 6000. Min: 1000. Max: 8760.

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?

No annotations exist, so the description carries the full burden and meets it: declares read-only, idempotent, stateless behavior with zero side effects, and specifies that out-of-bounds inputs return a safe diagnostic error rather than throwing. Determinism and floating-point precision are also stated up front.

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 formula, then cleanly sectioned into usage, boundaries, behavior, and returns. Minor redundancy: the four parameters are re-listed with units in the usage block, and the returns tree is long, though that length substitutes for the missing output schema.

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?

With no output schema and no annotations, the description fills both gaps: it enumerates every returned field including formatted metric strings and status/error semantics, and it covers validation behavior for a bounded-input calculator. An agent has everything needed to call and interpret results.

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% with defaults and min/max on all four parameters, so the schema already does the heavy lifting. The description only restates parameter names with units in the WHEN TO USE sentence; it adds no domain intuition (e.g. how speed percentage relates to flow, or typical cost ranges) beyond the schema.

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?

Names a specific tool ('Variable Frequency Drive (VFD) Pump Affinity Law Savings Calculator') and states exactly what it computes: energy savings and payback from installing a VFD on centrifugal pumps/fans via Affinity Laws. The formula (P₂ = P₁ · (RPM₂/RPM₁)³) and discipline tag make the resource unambiguous against generic siblings.

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?

Explicit WHEN TO USE with the exact output metrics and inputs, plus a WHEN NOT TO USE clause excluding qualitative/unquantified reasoning. Disambiguation section names concrete alternatives (omni_universal_query for generic dispatch, omni_batch_calculate for chained jobs, omni_describe_solver for schema inspection), so routing is fully determined.

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