Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_ev_charging_load

Calculate EV charging time, added miles per hour, charging power, and required breaker amps from battery size, state of charge, and charger voltage and current inputs.

Instructions

EV Charging Load, Time & Electrical Panel Capacity Calculator. Calculate charging speed (miles per hour), charge duration, breaker amperage, and continuous electrical panel load for electric vehicles across Level 1, 2, and 3 chargers. Discipline: ENERGY. Governing mathematical model / formula: Charging kW = (Volts × Amps × Power Factor) / 1000 | Charge Hours = Battery kWh Needed / Effective kW.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of charge_time_hrs (Time to Target Charge), charge_speed_mph (Charge Speed Added), charging_power_kw (Continuous Charging Power), breaker_req_amps (Minimum Circuit Breaker Required) using battery_size_kwh (EV Battery Pack Usable Capacity (kWh) in kWh), start_soc_pct (Starting State of Charge (SoC %) in %), target_soc_pct (Target State of Charge (SoC %) in %), charger_amps (Charging Current Rating (Amperes) in Amps), charger_volts (Supply Voltage (Volts AC) in V), ev_efficiency (Vehicle Driving Efficiency (mi/kWh) in mi/kWh). 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'EV Charging Load, Time & Electrical Panel Capacity Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

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): "ev-charging-load"

    • category (string): "energy"

    • name (string): "EV Charging Load, Time & Electrical Panel Capacity Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.charge_time_hrs (Time to Target Charge): Formatted display string (e.g. '4.3 hours')

      • metrics.charge_speed_mph (Charge Speed Added): Formatted display string (e.g. '35.2 mi/hr')

      • metrics.charging_power_kw (Continuous Charging Power): Formatted display string (e.g. '11.52 kW')

      • metrics.breaker_req_amps (Minimum Circuit Breaker Required): Formatted display string (e.g. '60 Amp Breaker')

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

Input Schema

NameRequiredDescriptionDefault
charger_ampsNoCharging Current Rating (Amperes) (Amps). Continuous current (NEC 80% rule requires 60A breaker for 48A load). Default: 48. Min: 12. Max: 80.
charger_voltsNoSupply Voltage (Volts AC) (V). 120V for Level 1, 240V for Level 2 residential. Default: 240. Min: 110. Max: 480.
ev_efficiencyNoVehicle Driving Efficiency (mi/kWh) (mi/kWh). Average miles per kilowatt-hour. Default: 3.4. Min: 1.5. Max: 5.
start_soc_pctNoStarting State of Charge (SoC %) (%). Current battery charge level. Default: 20. Min: 0. Max: 95.
target_soc_pctNoTarget State of Charge (SoC %) (%). Recommended daily charging ceiling (usually 80%). Default: 80. Min: 10. Max: 100.
battery_size_kwhNoEV Battery Pack Usable Capacity (kWh) (kWh). Usable battery pack size (e.g. Model Y = 75 kWh, Ioniq 5 = 77 kWh). Default: 77.4. Min: 20. Max: 200.

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 are supplied, so the description carries the full burden and it does: pure deterministic computation, read-only, idempotent, stateless, zero side effects, and out-of-bounds inputs return a diagnostic error status rather than throwing. It even explains the physical/domain-bound validation behavior the agent will observe on bad input.

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 front-loaded: purpose, then formula, then usage, behavior, returns. However, the WHEN TO USE clause re-lists all seven parameters with units and labels that are already verbatim in the schema, which is measurable redundancy in a description that is otherwise tight.

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?

There is no output schema, and the RETURNS block fully specifies the response envelope, the metrics keys with example formatted strings (e.g. '11.52 kW', '60 Amp Breaker'), and execution_time_ms. Combined with the governing formula and validation behavior, an agent has everything needed to call and interpret the tool.

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 units, defaults and min/max, including the NEC 80% rule. The description only repeats parameter names with their units in the WHEN TO USE block, adding no formatting or interaction semantics beyond the schema — baseline 3.

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+resource set: computes charging speed, charge duration, breaker amperage and continuous panel load for Level 1/2/3 chargers. It explicitly names the sibling it is not (omni_universal_query) and its scope is narrow enough to be distinguished from omni_ev_charging_cost.

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?

Has explicit WHEN TO USE (deterministic computation of the four named outputs from the seven named inputs), an explicit WHEN NOT TO USE (qualitative reasoning, non-numeric inputs), and SIBLING ROUTING naming omni_universal_query for cross-discipline dispatch. Nothing 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