calc.engineer

Official89 tools

by calc

88 free engineering calculators: RF link budgets, LoRa/Meshtastic, PCB, solar, homelab. Keyless.

engineer.calc/calc Model Context Protocol (MCP) Server

The engineer.calc/calc MCP server provides access to a collection of 88 free engineering calculators focused on domains such as RF link budgets, LoRa/Meshtastic, PCB design, solar, and homelab. It is described as keyless.

🛠️ Key Features

88 free engineering calculators
Calculator coverage includes: RF link budgets, LoRa/Meshtastic, PCB, solar, homelab
Keyless access model

🚀 Use Cases

Compute RF link budgets
Support calculations for LoRa/Meshtastic use cases
Perform PCB-related engineering calculations
Estimate or evaluate solar-related parameters
Aid homelab engineering tasks

Captured live from the server via tools/list.

fspl

Calculate free-space path loss (FSPL) in decibels using the ITU-R P.525 standard formula. Given a frequency in MHz and distance in kilometres, returns the expected signal attenuation in an ideal line-of-sight radio link with no obstacles, reflections, or atmospheric absorption. Also computes the RF wavelength. Use this to estimate baseline path loss before adding fade margins, antenna gains, or environmental corrections. Feeds directly into link_budget for full end-to-end analysis.

Parameters2

freq_mhz	number	required	Carrier frequency in megahertz (MHz)
dist_km	number	required	Distance between transmitter and receiver in kilometres

Raw schema

{
  "type": "object",
  "properties": {
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Carrier frequency in megahertz (MHz)"
    },
    "dist_km": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Distance between transmitter and receiver in kilometres"
    }
  },
  "required": [
    "freq_mhz",
    "dist_km"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

link_budget

Compute a full RF link budget from transmitter power, frequency, distance, and antenna gains. Calculates EIRP, free-space path loss (ITU-R P.525), received power at the receiver, and link margin relative to an optional receiver sensitivity threshold. Use this to determine whether a wireless link closes with adequate margin. Accepts output from noise_figure_cascade and feeds into snr_margin for full receive-chain analysis.

Parameters6

tx_dbm	number	required	Transmitter output power in dBm
freq_mhz	number	required	Carrier frequency in megahertz (MHz)
dist_km	number	required	Link distance in kilometres
tx_gain_dbi	number	optional	Transmit antenna gain in dBi (default 2.15 for a half-wave dipole)
rx_gain_dbi	number	optional	Receive antenna gain in dBi (default 2.15 for a half-wave dipole)
rx_sensitivity_dbm	number	optional	Receiver sensitivity in dBm; when provided, link margin is calculated

Raw schema

{
  "type": "object",
  "properties": {
    "tx_dbm": {
      "type": "number",
      "description": "Transmitter output power in dBm"
    },
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Carrier frequency in megahertz (MHz)"
    },
    "dist_km": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Link distance in kilometres"
    },
    "tx_gain_dbi": {
      "type": "number",
      "default": 2.15,
      "description": "Transmit antenna gain in dBi (default 2.15 for a half-wave dipole)"
    },
    "rx_gain_dbi": {
      "type": "number",
      "default": 2.15,
      "description": "Receive antenna gain in dBi (default 2.15 for a half-wave dipole)"
    },
    "rx_sensitivity_dbm": {
      "type": "number",
      "description": "Receiver sensitivity in dBm; when provided, link margin is calculated"
    }
  },
  "required": [
    "tx_dbm",
    "freq_mhz",
    "dist_km"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

dipole

Calculate physical dimensions of a dipole antenna for a given frequency. Returns half-wave or quarter-wave element length in metres, feet, and inches. A half-wave dipole is the most common resonant antenna with approximately 2.15 dBi gain. A quarter-wave monopole (ground plane antenna) is half the length and is widely used in handheld radios and vehicle-mounted systems. Use this before building or purchasing an antenna to verify element length for your operating frequency.

Parameters2

freq_mhz	number	required	Operating frequency in megahertz (MHz)
type	string	optional	Antenna type: half_wave dipole or quarter_wave monopole

Raw schema

{
  "type": "object",
  "properties": {
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Operating frequency in megahertz (MHz)"
    },
    "type": {
      "type": "string",
      "enum": [
        "half_wave",
        "quarter_wave"
      ],
      "default": "half_wave",
      "description": "Antenna type: half_wave dipole or quarter_wave monopole"
    }
  },
  "required": [
    "freq_mhz"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

microstrip

Calculate PCB microstrip trace width for a target characteristic impedance using the Hammerstad-Jensen closed-form equations. Given target impedance (Z0), substrate dielectric constant (er), substrate height, and copper weight, returns the required trace width and effective dielectric constant. Optionally computes effective wavelength at a given frequency. Essential for RF PCB layout to achieve controlled impedance traces (e.g. 50 ohm for SMA connectors). References IPC-2141.

Parameters5

z0_ohm	number	optional	Target characteristic impedance in ohms (default 50)
er	number	optional	Substrate relative dielectric constant (default 4.6 for FR-4)
height_mm	number	required	Substrate height (dielectric thickness) in millimetres
copper_oz	number	optional	Copper weight in oz/ft2 (1 oz = 0.035 mm thickness)
freq_mhz	number	optional	Optional frequency in MHz for effective wavelength calculation

Raw schema

{
  "type": "object",
  "properties": {
    "z0_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 50,
      "description": "Target characteristic impedance in ohms (default 50)"
    },
    "er": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 4.6,
      "description": "Substrate relative dielectric constant (default 4.6 for FR-4)"
    },
    "height_mm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Substrate height (dielectric thickness) in millimetres"
    },
    "copper_oz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Copper weight in oz/ft2 (1 oz = 0.035 mm thickness)"
    },
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Optional frequency in MHz for effective wavelength calculation"
    }
  },
  "required": [
    "height_mm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

dbm_convert

Convert a power level in dBm to milliwatts, watts, dBW, and RMS voltage across a given impedance. dBm is the standard unit for RF power referenced to 1 milliwatt. This tool is essential when interfacing datasheets (which use dBm) with circuit analysis (which uses volts and watts). Default impedance is 50 ohms, matching most RF systems. Use this to quickly verify power amplifier output, receiver sensitivity, or regulatory EIRP limits.

Parameters2

dbm	number	required	Power level in dBm (decibels relative to 1 milliwatt)
impedance_ohm	number	optional	Load impedance in ohms for Vrms calculation (default 50)

Raw schema

{
  "type": "object",
  "properties": {
    "dbm": {
      "type": "number",
      "description": "Power level in dBm (decibels relative to 1 milliwatt)"
    },
    "impedance_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 50,
      "description": "Load impedance in ohms for Vrms calculation (default 50)"
    }
  },
  "required": [
    "dbm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

noise_figure_cascade

Calculate the cascaded noise figure of a multi-stage receiver chain using the Friis formula. Each stage has a noise figure and gain in dB. The first stage dominates overall system noise, which is why low-noise amplifiers (LNAs) are placed at the front of the chain. Returns total cascaded noise figure, total gain, and equivalent noise temperature. Feeds into link_budget for complete receive-chain sensitivity analysis.

Parameters1

stages

array

required

Ordered array of receiver chain stages, each with nf_db and gain_db

Raw schema

{
  "type": "object",
  "properties": {
    "stages": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "nf_db": {
            "type": "number",
            "description": "Noise figure of the stage in dB"
          },
          "gain_db": {
            "type": "number",
            "description": "Gain of the stage in dB"
          }
        },
        "required": [
          "nf_db",
          "gain_db"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "Ordered array of receiver chain stages, each with nf_db and gain_db"
    }
  },
  "required": [
    "stages"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

vswr

Convert between VSWR, return loss, and reflection coefficient — provide any one parameter and get all related impedance-mismatch metrics. Computes VSWR (voltage standing wave ratio), return loss in dB, reflection coefficient (gamma), mismatch loss, and percentage of power reflected vs transmitted. Essential for antenna matching, transmission line analysis, and RF system budgeting. Feeds into link_budget for system-level mismatch accounting.

Parameters3

vswr	number	optional	Voltage standing wave ratio (>= 1.0, where 1.0 is perfect match)
return_loss_db	number	optional	Return loss in decibels (positive value, higher is better match)
reflection_coefficient	number	optional	Reflection coefficient magnitude (gamma), 0 to 1

Raw schema

{
  "type": "object",
  "properties": {
    "vswr": {
      "type": "number",
      "minimum": 1,
      "description": "Voltage standing wave ratio (>= 1.0, where 1.0 is perfect match)"
    },
    "return_loss_db": {
      "type": "number",
      "minimum": 0,
      "description": "Return loss in decibels (positive value, higher is better match)"
    },
    "reflection_coefficient": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "description": "Reflection coefficient magnitude (gamma), 0 to 1"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

attenuator_pi

Design a Pi-topology resistive attenuator pad. Given a desired attenuation in dB and characteristic impedance (default 50 ohm), computes the three resistor values for a symmetrical Pi-pad network. The Pi attenuator uses two shunt resistors (R1, R3) and one series resistor (R2). Commonly used in RF signal chains to reduce signal level while maintaining impedance match. Compare with attenuator_tee for T-pad topology.

Parameters2

attenuation_db	number	required	Desired attenuation in decibels (positive value)
z0_ohm	number	optional	Characteristic impedance in ohms (default 50)

Raw schema

{
  "type": "object",
  "properties": {
    "attenuation_db": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Desired attenuation in decibels (positive value)"
    },
    "z0_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 50,
      "description": "Characteristic impedance in ohms (default 50)"
    }
  },
  "required": [
    "attenuation_db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

attenuator_tee

Design a Tee-topology resistive attenuator pad. Given a desired attenuation in dB and characteristic impedance (default 50 ohm), computes the three resistor values for a symmetrical T-pad network. The Tee attenuator uses two series resistors (R1, R3) and one shunt resistor (R2). Commonly used in RF signal chains to reduce signal level while maintaining impedance match. Compare with attenuator_pi for Pi-pad topology.

Parameters2

attenuation_db	number	required	Desired attenuation in decibels (positive value)
z0_ohm	number	optional	Characteristic impedance in ohms (default 50)

Raw schema

{
  "type": "object",
  "properties": {
    "attenuation_db": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Desired attenuation in decibels (positive value)"
    },
    "z0_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 50,
      "description": "Characteristic impedance in ohms (default 50)"
    }
  },
  "required": [
    "attenuation_db"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

fresnel_zone

Calculate the Fresnel zone radius at the midpoint of a radio link. Given frequency in MHz, link distance in kilometres, and zone number (1-5), returns the Fresnel zone radius in metres and feet, plus the 60% clearance threshold used in practical link engineering. The first Fresnel zone defines the region where most RF energy travels; obstructions within 60% of this radius cause significant signal degradation. Feeds into link_budget for path clearance analysis.

Parameters3

freq_mhz	number	required	Operating frequency in megahertz (MHz)
dist_km	number	required	Total link distance in kilometres
zone_number	integer	optional	Fresnel zone number (1-5, default 1)

Raw schema

{
  "type": "object",
  "properties": {
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Operating frequency in megahertz (MHz)"
    },
    "dist_km": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total link distance in kilometres"
    },
    "zone_number": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "default": 1,
      "description": "Fresnel zone number (1-5, default 1)"
    }
  },
  "required": [
    "freq_mhz",
    "dist_km"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

wavelength_freq

Convert between radio frequency and wavelength. Provide either frequency in MHz or wavelength in metres, and get the full set of equivalent values: frequency in MHz and GHz, wavelength in metres, centimetres, millimetres, and feet. Essential for antenna dimensioning, waveguide selection, and quick band identification. The fundamental relationship is lambda = c / f where c is the speed of light (299 792 458 m/s).

Parameters2

freq_mhz	number	optional	Frequency in megahertz (MHz)
wavelength_m	number	optional	Wavelength in metres

Raw schema

{
  "type": "object",
  "properties": {
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Frequency in megahertz (MHz)"
    },
    "wavelength_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Wavelength in metres"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

spice_template

Generate a complete SPICE netlist from a parameterized template. Supports common circuit topologies: low-pass RC filter, voltage divider, common emitter amplifier. Returns a ready-to-simulate netlist string that can be passed directly to spice_simulate. Use this when an agent needs to construct a circuit from high-level parameters without writing raw SPICE syntax. Feeds into spice_simulate for AC/DC/transient analysis.

Parameters3

template	string	required	Circuit template name
params	object	required	Template-specific parameters (e.g. r_ohms, c_farads, v_source)
analysis	string	optional	SPICE analysis type to include in netlist

Raw schema

{
  "type": "object",
  "properties": {
    "template": {
      "type": "string",
      "enum": [
        "low_pass_rc",
        "voltage_divider",
        "common_emitter",
        "rc_highpass",
        "rlc_bandpass",
        "opamp_inverting",
        "diode_rectifier",
        "wien_bridge"
      ],
      "description": "Circuit template name"
    },
    "params": {
      "type": "object",
      "additionalProperties": {
        "type": "number"
      },
      "description": "Template-specific parameters (e.g. r_ohms, c_farads, v_source)"
    },
    "analysis": {
      "type": "string",
      "enum": [
        "ac",
        "dc",
        "tran"
      ],
      "default": "ac",
      "description": "SPICE analysis type to include in netlist"
    }
  },
  "required": [
    "template",
    "params"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

spice_simulate

Run a SPICE circuit simulation directly in the worker. Accepts a standard SPICE netlist and performs operating-point (.op), DC sweep (.dc), AC frequency sweep (.ac), or transient (.tran) analysis using a built-in modified-nodal-analysis engine with Newton-Raphson nonlinear solving. Supports R, L, C, V, I sources (DC/AC/SIN/PULSE), diodes, BJTs (Ebers-Moll), MOSFETs (Shichman-Hodges level 1), controlled sources (E/G), .param expressions, .subckt/X hierarchical subcircuits, .measure and .four (Fourier/THD), and a built-in parts library (reference 2n3904/2n2222/1n4148/1n5819/2n7000/tl072/lm358/led_red etc. by name and the model is auto-injected), up to 150 components. Returns voltage vectors for all circuit nodes (magnitude + phase for AC). Use spice_template to generate netlists from parameterized templates.

Parameters7

netlist	string	required	SPICE netlist (ngspice-compatible). Must include at least one analysis command (.ac, .dc, .tran, .op) and end with .end
analysis	string	optional	Override analysis type (auto-detected from netlist if omitted)
temperature_c	number	optional	Simulation temperature in Celsius
options	object	optional	Additional ngspice .options (e.g. { reltol: 0.001 })
certify	boolean	optional	If true, attach an a-posteriori existence certificate for the DC operating point (Newton–Kantorovich: proves a true solution exists within a computed radius, or refuses). Adds ~one extra back-solve.
tolerances	object	optional	Component-tolerance box, e.g. {"R1":0.05,"V1":0.02} (fractional). With output_node, returns a certified min/max interval for that node over all component variations. R/V/I elements only.
output_node	string	optional	Node whose voltage is certified over the tolerance box (required with tolerances).

Raw schema

{
  "type": "object",
  "properties": {
    "netlist": {
      "type": "string",
      "minLength": 10,
      "description": "SPICE netlist (ngspice-compatible). Must include at least one analysis command (.ac, .dc, .tran, .op) and end with .end"
    },
    "analysis": {
      "type": "string",
      "enum": [
        "ac",
        "dc",
        "tran",
        "op"
      ],
      "description": "Override analysis type (auto-detected from netlist if omitted)"
    },
    "temperature_c": {
      "type": "number",
      "default": 27,
      "description": "Simulation temperature in Celsius"
    },
    "options": {
      "type": "object",
      "additionalProperties": {
        "type": [
          "string",
          "number",
          "boolean"
        ]
      },
      "description": "Additional ngspice .options (e.g. { reltol: 0.001 })"
    },
    "certify": {
      "type": "boolean",
      "description": "If true, attach an a-posteriori existence certificate for the DC operating point (Newton–Kantorovich: proves a true solution exists within a computed radius, or refuses). Adds ~one extra back-solve."
    },
    "tolerances": {
      "type": "object",
      "additionalProperties": {
        "type": "number"
      },
      "description": "Component-tolerance box, e.g. {\"R1\":0.05,\"V1\":0.02} (fractional). With output_node, returns a certified min/max interval for that node over all component variations. R/V/I elements only."
    },
    "output_node": {
      "type": "string",
      "description": "Node whose voltage is certified over the tolerance box (required with tolerances)."
    }
  },
  "required": [
    "netlist"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lora_airtime

Calculates LoRa packet time-on-air using the Semtech AN1200.13 formula. Computes symbol duration, preamble time, payload symbol count, effective data rate, and the minimum transmission interval for 1% duty cycle compliance. Essential for capacity planning in LoRaWAN and Meshtastic mesh networks. Accepts spreading factor (SF7-SF12), bandwidth (125/250/500 kHz), coding rate (4/5-4/8), payload size, header mode, CRC, and optional low data rate optimization. Feeds airtime_ms to channel_utilization for mesh load analysis.

Parameters8

sf	integer	optional	LoRa spreading factor (7-12). Higher SF = longer range but slower data rate.
bw_khz	number	optional	LoRa channel bandwidth in kHz. Common values: 125, 250, or 500.
cr	integer	optional	LoRa coding rate denominator (5-8). Represents 4/5 through 4/8 FEC ratio.
payload_bytes	integer	required	Application payload size in bytes (0-255).
preamble_symbols	integer	optional	Number of preamble symbols. LoRaWAN uses 8; raw LoRa may vary.
explicit_header	boolean	optional	Whether to use explicit header mode. True for LoRaWAN; false for implicit header.
crc	boolean	optional	Whether CRC is appended to payload. Recommended true for reliability.
low_data_rate_optimize	boolean	optional	Enable low data rate optimization. Auto-calculated if omitted: enabled for SF >= 11 at BW 125 kHz.

Raw schema

{
  "type": "object",
  "properties": {
    "sf": {
      "type": "integer",
      "minimum": 7,
      "maximum": 12,
      "default": 10,
      "description": "LoRa spreading factor (7-12). Higher SF = longer range but slower data rate."
    },
    "bw_khz": {
      "type": "number",
      "enum": [
        125,
        250,
        500
      ],
      "default": 125,
      "description": "LoRa channel bandwidth in kHz. Common values: 125, 250, or 500."
    },
    "cr": {
      "type": "integer",
      "minimum": 5,
      "maximum": 8,
      "default": 5,
      "description": "LoRa coding rate denominator (5-8). Represents 4/5 through 4/8 FEC ratio."
    },
    "payload_bytes": {
      "type": "integer",
      "minimum": 0,
      "maximum": 255,
      "description": "Application payload size in bytes (0-255)."
    },
    "preamble_symbols": {
      "type": "integer",
      "minimum": 6,
      "maximum": 65535,
      "default": 8,
      "description": "Number of preamble symbols. LoRaWAN uses 8; raw LoRa may vary."
    },
    "explicit_header": {
      "type": "boolean",
      "default": true,
      "description": "Whether to use explicit header mode. True for LoRaWAN; false for implicit header."
    },
    "crc": {
      "type": "boolean",
      "default": true,
      "description": "Whether CRC is appended to payload. Recommended true for reliability."
    },
    "low_data_rate_optimize": {
      "type": "boolean",
      "description": "Enable low data rate optimization. Auto-calculated if omitted: enabled for SF >= 11 at BW 125 kHz."
    }
  },
  "required": [
    "payload_bytes"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

snr_margin

Computes LoRa link SNR margin by comparing received power against the noise floor and the spreading-factor-dependent demodulation threshold from the Semtech SX1276 datasheet. Calculates receiver noise floor from thermal noise (-174 dBm/Hz), channel bandwidth, and receiver noise figure. Returns margin in dB and a boolean link-OK indicator. Use to validate whether a LoRa or Meshtastic link will reliably decode packets. Accepts rx_power from link_budget tool output for end-to-end chain analysis.

Parameters4

rx_power_dbm	number	required	Received signal power in dBm (e.g., -110). Typically from a link budget calculation or field measurement.
sf	integer	optional	LoRa spreading factor (7-12). Higher SF tolerates lower SNR.
bw_khz	number	optional	LoRa channel bandwidth in kHz. Affects noise floor.
noise_figure_db	number	optional	Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276).

Raw schema

{
  "type": "object",
  "properties": {
    "rx_power_dbm": {
      "type": "number",
      "description": "Received signal power in dBm (e.g., -110). Typically from a link budget calculation or field measurement."
    },
    "sf": {
      "type": "integer",
      "minimum": 7,
      "maximum": 12,
      "default": 10,
      "description": "LoRa spreading factor (7-12). Higher SF tolerates lower SNR."
    },
    "bw_khz": {
      "type": "number",
      "enum": [
        125,
        250,
        500
      ],
      "default": 125,
      "description": "LoRa channel bandwidth in kHz. Affects noise floor."
    },
    "noise_figure_db": {
      "type": "number",
      "default": 6,
      "description": "Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276)."
    }
  },
  "required": [
    "rx_power_dbm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

channel_utilization

Estimates Meshtastic or LoRa mesh channel utilization percentage based on node count, message rate, and per-packet airtime. Determines how much of the shared radio channel is occupied and computes the maximum number of nodes before exceeding a configurable duty cycle limit (default 10%). Returns utilization percentage, headroom, and total packet count. Chain from lora_airtime to get airtime_ms input. Essential for Meshtastic mesh deployment planning to avoid channel congestion and packet collisions.

Parameters4

nodes	integer	required	Number of active nodes in the mesh network.
messages_per_hour_per_node	number	optional	Average messages transmitted per hour per node. Includes position beacons and user messages.
airtime_ms	number	required	Time-on-air per packet in milliseconds. Obtain from lora_airtime tool.
max_duty_cycle_pct	number	optional	Maximum acceptable channel utilization percentage. Default 10% is a common Meshtastic guideline.

Raw schema

{
  "type": "object",
  "properties": {
    "nodes": {
      "type": "integer",
      "minimum": 1,
      "description": "Number of active nodes in the mesh network."
    },
    "messages_per_hour_per_node": {
      "type": "number",
      "minimum": 0,
      "default": 2,
      "description": "Average messages transmitted per hour per node. Includes position beacons and user messages."
    },
    "airtime_ms": {
      "type": "number",
      "minimum": 0,
      "description": "Time-on-air per packet in milliseconds. Obtain from lora_airtime tool."
    },
    "max_duty_cycle_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 10,
      "description": "Maximum acceptable channel utilization percentage. Default 10% is a common Meshtastic guideline."
    }
  },
  "required": [
    "nodes",
    "airtime_ms"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lora_range_estimate

Estimates LoRa maximum communication range by computing the free-space path loss (FSPL) link budget and applying terrain-dependent correction factors. Calculates total link budget from transmit power, antenna gains, and receiver sensitivity, then solves the FSPL equation for distance after subtracting terrain losses (0 dB open to 50 dB indoor). Returns estimated range in km, link margin at 1 km, and effective path loss. Useful for Meshtastic deployment planning and coverage mapping. Terrain corrections are empirical estimates; real-world range varies with elevation, foliage, and weather.

Parameters6

tx_dbm	number	optional	Transmit power in dBm. Typical LoRa: 14-30 dBm depending on region and module.
freq_mhz	number	optional	Carrier frequency in MHz. Common: 868 (EU), 915 (US/AU), 433 (Asia).
tx_gain_dbi	number	optional	Transmit antenna gain in dBi. 2.15 dBi = half-wave dipole.
rx_gain_dbi	number	optional	Receive antenna gain in dBi. 2.15 dBi = half-wave dipole.
rx_sensitivity_dbm	number	optional	Receiver sensitivity in dBm. Typical LoRa SF10/BW125: -130 dBm. Varies by SF and bandwidth.
terrain	string	optional	Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.

Raw schema

{
  "type": "object",
  "properties": {
    "tx_dbm": {
      "type": "number",
      "default": 20,
      "description": "Transmit power in dBm. Typical LoRa: 14-30 dBm depending on region and module."
    },
    "freq_mhz": {
      "type": "number",
      "default": 915,
      "description": "Carrier frequency in MHz. Common: 868 (EU), 915 (US/AU), 433 (Asia)."
    },
    "tx_gain_dbi": {
      "type": "number",
      "default": 2.15,
      "description": "Transmit antenna gain in dBi. 2.15 dBi = half-wave dipole."
    },
    "rx_gain_dbi": {
      "type": "number",
      "default": 2.15,
      "description": "Receive antenna gain in dBi. 2.15 dBi = half-wave dipole."
    },
    "rx_sensitivity_dbm": {
      "type": "number",
      "default": -130,
      "description": "Receiver sensitivity in dBm. Typical LoRa SF10/BW125: -130 dBm. Varies by SF and bandwidth."
    },
    "terrain": {
      "type": "string",
      "enum": [
        "open",
        "suburban",
        "urban",
        "dense_urban",
        "indoor"
      ],
      "default": "suburban",
      "description": "Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lora_sensitivity

Calculates LoRa receiver sensitivity from spreading factor, bandwidth, and noise figure using the Semtech SX1276 datasheet SNR thresholds. Computes the noise floor from thermal noise density (-174 dBm/Hz), channel bandwidth, and receiver noise figure, then adds the spreading-factor-dependent minimum demodulation SNR. Returns sensitivity in dBm, noise floor, required SNR, and thermal noise reference. Essential for link budget planning in LoRaWAN and Meshtastic networks. Feeds sensitivity_dbm to link_budget and lora_range_estimate for end-to-end coverage analysis.

Parameters3

sf	integer	optional	LoRa spreading factor (7-12). Higher SF = better sensitivity but slower data rate.
bw_khz	number	optional	LoRa channel bandwidth in kHz. Lower bandwidth = better sensitivity.
noise_figure_db	number	optional	Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276).

Raw schema

{
  "type": "object",
  "properties": {
    "sf": {
      "type": "integer",
      "minimum": 7,
      "maximum": 12,
      "default": 10,
      "description": "LoRa spreading factor (7-12). Higher SF = better sensitivity but slower data rate."
    },
    "bw_khz": {
      "type": "number",
      "enum": [
        125,
        250,
        500
      ],
      "default": 125,
      "description": "LoRa channel bandwidth in kHz. Lower bandwidth = better sensitivity."
    },
    "noise_figure_db": {
      "type": "number",
      "default": 6,
      "description": "Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276)."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

duty_cycle_budget

Calculates LoRa duty cycle budget for EU868, US915, AS923, and AU915 regulatory regions. Computes maximum messages per hour, minimum transmission interval, and effective data rate under regional duty cycle constraints. EU868 and AS923 enforce 1% duty cycle (ETSI); US915 has no duty cycle limit but a 400 ms dwell time per channel (FCC); AU915 has no duty cycle limit. Flags dwell-time-limited regions where packet airtime must not exceed the dwell time. Chain from lora_airtime to get airtime_ms input for end-to-end regulatory compliance analysis.

Parameters2

airtime_ms	number	required	Packet time-on-air in milliseconds. Obtain from the lora_airtime tool.
region	string	optional	LoRa regulatory region. EU868: 1% duty cycle (ETSI). US915: no duty cycle but 400 ms dwell time (FCC). AS923: 1% duty cycle (varies by country). AU915: no duty cycle limit.

Raw schema

{
  "type": "object",
  "properties": {
    "airtime_ms": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Packet time-on-air in milliseconds. Obtain from the lora_airtime tool."
    },
    "region": {
      "type": "string",
      "enum": [
        "EU868",
        "US915",
        "AS923",
        "AU915"
      ],
      "default": "EU868",
      "description": "LoRa regulatory region. EU868: 1% duty cycle (ETSI). US915: no duty cycle but 400 ms dwell time (FCC). AS923: 1% duty cycle (varies by country). AU915: no duty cycle limit."
    }
  },
  "required": [
    "airtime_ms"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

meshtastic_range

Estimates Meshtastic node communication range using real hardware profiles and firmware channel presets. Combines device-specific TX power and antenna gain (Heltec V3, RAK WisBlock, T-Beam, T-Beam Supreme, Station G2) with firmware modem presets (Long Fast, Long Slow, Very Long Slow, Medium, Short) to compute receiver sensitivity and FSPL-based range with terrain correction. Automatically populates LoRa parameters from device and channel selection, with optional overrides for custom antennas or power levels. Essential for Meshtastic deployment planning and node placement. Returns range, sensitivity, link budget, and the effective radio parameters used.

Parameters8

device	string	optional	Meshtastic hardware device. Selects default TX power, antenna gain, and noise figure. Use 'custom' to override all radio parameters manually.
channel_preset	string	optional	Meshtastic firmware channel preset. Selects spreading factor, bandwidth, and coding rate. long_fast is the default; very_long_slow maximizes range at the cost of throughput.
terrain	string	optional	Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.
antenna_gain_dbi	number	optional	Override device default antenna gain in dBi. Useful for aftermarket antennas.
tx_power_dbm	number	optional	Override device default transmit power in dBm.
sf	integer	optional	Custom spreading factor (7-12). Only used when channel_preset is 'custom'.
bw_khz	number	optional	Custom bandwidth in kHz. Only used when channel_preset is 'custom'.
cr	integer	optional	Custom coding rate denominator (5-8). Only used when channel_preset is 'custom'.

Raw schema

{
  "type": "object",
  "properties": {
    "device": {
      "type": "string",
      "enum": [
        "heltec_v3",
        "rak_wisblock",
        "tbeam",
        "tbeam_supreme",
        "station_g2",
        "custom"
      ],
      "default": "heltec_v3",
      "description": "Meshtastic hardware device. Selects default TX power, antenna gain, and noise figure. Use 'custom' to override all radio parameters manually."
    },
    "channel_preset": {
      "type": "string",
      "enum": [
        "long_fast",
        "long_moderate",
        "long_slow",
        "very_long_slow",
        "medium_fast",
        "medium_slow",
        "short_fast",
        "short_slow",
        "custom"
      ],
      "default": "long_fast",
      "description": "Meshtastic firmware channel preset. Selects spreading factor, bandwidth, and coding rate. long_fast is the default; very_long_slow maximizes range at the cost of throughput."
    },
    "terrain": {
      "type": "string",
      "enum": [
        "open",
        "suburban",
        "urban",
        "dense_urban",
        "indoor"
      ],
      "default": "suburban",
      "description": "Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings."
    },
    "antenna_gain_dbi": {
      "type": "number",
      "description": "Override device default antenna gain in dBi. Useful for aftermarket antennas."
    },
    "tx_power_dbm": {
      "type": "number",
      "description": "Override device default transmit power in dBm."
    },
    "sf": {
      "type": "integer",
      "minimum": 7,
      "maximum": 12,
      "description": "Custom spreading factor (7-12). Only used when channel_preset is 'custom'."
    },
    "bw_khz": {
      "type": "number",
      "description": "Custom bandwidth in kHz. Only used when channel_preset is 'custom'."
    },
    "cr": {
      "type": "integer",
      "minimum": 5,
      "maximum": 8,
      "description": "Custom coding rate denominator (5-8). Only used when channel_preset is 'custom'."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

eirp_compliance

Checks EIRP (Effective Isotropic Radiated Power) compliance against regional regulatory limits for LoRa and Meshtastic operation. Computes EIRP from transmit power, antenna gain, and cable loss, then compares against FCC (US, 36 dBm), ETSI (EU, 16.15 dBm), ACMA (Australia, 30 dBm), IC (Canada, 36 dBm), and ARIB (Japan, 13 dBm) limits. Returns compliance status, margin in dB, and a warning message if over the limit. Critical for Meshtastic deployments using aftermarket high-gain antennas which can easily exceed ETSI/JP limits. Accepts tx_power and antenna_gain from meshtastic_range for chain validation.

Parameters5

tx_power_dbm	number	required	Conducted transmit power at the radio output in dBm. Typical LoRa: 14-22 dBm.
antenna_gain_dbi	number	required	Antenna gain in dBi. Stock Meshtastic antennas: 2-3 dBi. External: 6-10+ dBi.
cable_loss_db	number	optional	Coaxial cable and connector loss in dB. Set 0 for devices with integrated antennas.
region	string	optional	Regulatory region for EIRP limit lookup. FCC_US: 36 dBm, ETSI_EU: ~16 dBm, ACMA_AU: 30 dBm, IC_CA: 36 dBm, JP: 13 dBm.
custom_limit_dbm	number	optional	Custom EIRP limit in dBm. Only used when region is 'custom'.

Raw schema

{
  "type": "object",
  "properties": {
    "tx_power_dbm": {
      "type": "number",
      "description": "Conducted transmit power at the radio output in dBm. Typical LoRa: 14-22 dBm."
    },
    "antenna_gain_dbi": {
      "type": "number",
      "description": "Antenna gain in dBi. Stock Meshtastic antennas: 2-3 dBi. External: 6-10+ dBi."
    },
    "cable_loss_db": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Coaxial cable and connector loss in dB. Set 0 for devices with integrated antennas."
    },
    "region": {
      "type": "string",
      "enum": [
        "FCC_US",
        "ETSI_EU",
        "ACMA_AU",
        "IC_CA",
        "JP",
        "custom"
      ],
      "default": "FCC_US",
      "description": "Regulatory region for EIRP limit lookup. FCC_US: 36 dBm, ETSI_EU: ~16 dBm, ACMA_AU: 30 dBm, IC_CA: 36 dBm, JP: 13 dBm."
    },
    "custom_limit_dbm": {
      "type": "number",
      "description": "Custom EIRP limit in dBm. Only used when region is 'custom'."
    }
  },
  "required": [
    "tx_power_dbm",
    "antenna_gain_dbi"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

meshtastic_power

Calculates Meshtastic node power consumption and battery runtime using device-specific power profiles and firmware role-based duty cycling. Models sleep, RX, and TX current draw for Heltec V3, RAK WisBlock, T-Beam, T-Beam Supreme, and Station G2 with GPS, BLE, and display peripheral toggles. Role selection (client, router, repeater, client_muted) controls the duty cycle model: routers stay in RX mode continuously while clients sleep between events. Returns average current, runtime in hours/days, daily Wh consumption, and time distribution across TX/RX/sleep states. Feed daily_wh to solar_sizing for off-grid planning.

Parameters8

device	string	optional	Meshtastic hardware device. Selects power consumption profile for sleep, RX, TX, GPS, and BLE.
channel_preset	string	optional	Meshtastic channel preset. Affects TX airtime per message and thus power consumption.
battery_mah	number	optional	Battery capacity in milliamp-hours. Common: 1100 (18650 min), 3000 (typical), 6000 (large).
battery_voltage	number	optional	Nominal battery voltage. 3.7V for single-cell LiPo/Li-ion, 7.4V for 2S packs.
messages_per_hour	number	optional	Expected messages sent and received per hour. Includes both TX and RX message events.
gps_enabled	boolean	optional	Whether GPS is enabled. Significantly increases power draw on devices with built-in GPS.
bluetooth_enabled	boolean	optional	Whether Bluetooth is enabled for phone connection.
role	string	optional	Meshtastic node role. client: sleeps between events. router: always listening. repeater: always listening, no display/BLE. client_muted: aggressive sleep.

Raw schema

{
  "type": "object",
  "properties": {
    "device": {
      "type": "string",
      "enum": [
        "heltec_v3",
        "rak_wisblock",
        "tbeam",
        "tbeam_supreme",
        "station_g2",
        "custom"
      ],
      "default": "heltec_v3",
      "description": "Meshtastic hardware device. Selects power consumption profile for sleep, RX, TX, GPS, and BLE."
    },
    "channel_preset": {
      "type": "string",
      "enum": [
        "long_fast",
        "long_moderate",
        "long_slow",
        "very_long_slow",
        "medium_fast",
        "medium_slow",
        "short_fast",
        "short_slow"
      ],
      "default": "long_fast",
      "description": "Meshtastic channel preset. Affects TX airtime per message and thus power consumption."
    },
    "battery_mah": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3000,
      "description": "Battery capacity in milliamp-hours. Common: 1100 (18650 min), 3000 (typical), 6000 (large)."
    },
    "battery_voltage": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3.7,
      "description": "Nominal battery voltage. 3.7V for single-cell LiPo/Li-ion, 7.4V for 2S packs."
    },
    "messages_per_hour": {
      "type": "number",
      "minimum": 0,
      "default": 2,
      "description": "Expected messages sent and received per hour. Includes both TX and RX message events."
    },
    "gps_enabled": {
      "type": "boolean",
      "default": false,
      "description": "Whether GPS is enabled. Significantly increases power draw on devices with built-in GPS."
    },
    "bluetooth_enabled": {
      "type": "boolean",
      "default": true,
      "description": "Whether Bluetooth is enabled for phone connection."
    },
    "role": {
      "type": "string",
      "enum": [
        "client",
        "router",
        "repeater",
        "client_muted"
      ],
      "default": "client",
      "description": "Meshtastic node role. client: sleeps between events. router: always listening. repeater: always listening, no display/BLE. client_muted: aggressive sleep."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lora_param_optimizer

Recommends optimal LoRa spreading factor, bandwidth, and TX power based on target range, terrain, and optimization priority. Iterates through all SF (7-12) and BW (125/250/500 kHz) combinations, computing achievable range, airtime, data rate, and battery impact for each. Ranks candidates by priority: 'range' maximizes distance, 'speed' minimizes airtime, 'battery' minimizes power consumption, 'balanced' penalizes extremes. Respects regional TX power limits (FCC/ETSI/ACMA) and duty cycle constraints. Returns the recommended parameters with estimated range, airtime, duty-cycle message limit, battery life, and data rate. Essential for tuning Meshtastic and LoRa deployments to specific requirements.

Parameters6

target_range_km	number	required	Desired communication range in kilometers.
terrain	string	optional	Terrain type for path loss model. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.
max_payload_bytes	integer	optional	Maximum payload size in bytes for airtime calculation.
priority	string	optional	Optimization priority. range: maximize distance (high SF, low BW). speed: minimize airtime (low SF, high BW). battery: minimize power draw. balanced: best trade-off across all factors.
region	string	optional	Regulatory region. Determines max TX power and duty cycle limit.
antenna_gain_dbi	number	optional	Antenna gain in dBi. 2.15 = half-wave dipole reference.

Raw schema

{
  "type": "object",
  "properties": {
    "target_range_km": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Desired communication range in kilometers."
    },
    "terrain": {
      "type": "string",
      "enum": [
        "open",
        "suburban",
        "urban",
        "dense_urban",
        "indoor"
      ],
      "default": "suburban",
      "description": "Terrain type for path loss model. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings."
    },
    "max_payload_bytes": {
      "type": "integer",
      "minimum": 1,
      "maximum": 255,
      "default": 200,
      "description": "Maximum payload size in bytes for airtime calculation."
    },
    "priority": {
      "type": "string",
      "enum": [
        "range",
        "speed",
        "battery",
        "balanced"
      ],
      "default": "balanced",
      "description": "Optimization priority. range: maximize distance (high SF, low BW). speed: minimize airtime (low SF, high BW). battery: minimize power draw. balanced: best trade-off across all factors."
    },
    "region": {
      "type": "string",
      "enum": [
        "US915",
        "EU868",
        "AU915",
        "AS923"
      ],
      "default": "US915",
      "description": "Regulatory region. Determines max TX power and duty cycle limit."
    },
    "antenna_gain_dbi": {
      "type": "number",
      "default": 2.15,
      "description": "Antenna gain in dBi. 2.15 = half-wave dipole reference."
    }
  },
  "required": [
    "target_range_km"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

zfs_capacity

Calculate usable ZFS pool capacity for any RAID level including stripe, mirror, raidz1, raidz2, and raidz3. Computes raw capacity, parity overhead, data disk count, usable terabytes after ZFS metadata overhead (checksums, block pointers, uberblocks), and storage efficiency percentage. Essential for planning NAS builds, TrueNAS/ZFS server storage, and estimating how much usable space a given disk configuration will provide. Supports variable disk sizes and configurable metadata overhead.

Parameters5

disk_count	integer	required	Total number of physical disks in the pool
disk_size_tb	number	required	Size of each individual disk in terabytes
raid_type	string	optional	ZFS RAID level: stripe (no redundancy), mirror (2-way), raidz1/2/3 (single/double/triple parity)
record_size_kb	number	optional	ZFS record size in kilobytes, affects compression and performance
metadata_overhead_pct	number	optional	Percentage of raw capacity consumed by ZFS metadata, checksums, and internal structures

Raw schema

{
  "type": "object",
  "properties": {
    "disk_count": {
      "type": "integer",
      "minimum": 1,
      "description": "Total number of physical disks in the pool"
    },
    "disk_size_tb": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Size of each individual disk in terabytes"
    },
    "raid_type": {
      "type": "string",
      "enum": [
        "stripe",
        "mirror",
        "raidz1",
        "raidz2",
        "raidz3"
      ],
      "default": "raidz1",
      "description": "ZFS RAID level: stripe (no redundancy), mirror (2-way), raidz1/2/3 (single/double/triple parity)"
    },
    "record_size_kb": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 128,
      "description": "ZFS record size in kilobytes, affects compression and performance"
    },
    "metadata_overhead_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 3.2,
      "description": "Percentage of raw capacity consumed by ZFS metadata, checksums, and internal structures"
    }
  },
  "required": [
    "disk_count",
    "disk_size_tb"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

zfs_ram

Calculate recommended RAM and ARC sizing for a ZFS storage pool based on workload type, pool size, deduplication status, and L2ARC cache size. Computes minimum and recommended RAM in gigabytes, ARC target size, and dedup table overhead. Accounts for workload-specific IO patterns: NAS (sequential, 1GB/TB), database (random, 2GB/TB), virtualization (mixed, 1.5GB/TB). Deduplication adds approximately 5GB per TB for the DDT. L2ARC index requires 1GB RAM per 10GB of L2ARC. Essential for TrueNAS, FreeNAS, and custom ZFS server builds.

Parameters4

pool_size_tb	number	required	Total usable pool size in terabytes
workload	string	optional	Primary workload type: general (mixed), nas (sequential reads/writes), database (random IO), virtualization (mixed random)
dedup_enabled	boolean	optional	Whether ZFS deduplication is enabled (significantly increases RAM requirements)
l2arc_size_gb	number	optional	Size of L2ARC (read cache SSD) in gigabytes; requires additional RAM for index

Raw schema

{
  "type": "object",
  "properties": {
    "pool_size_tb": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total usable pool size in terabytes"
    },
    "workload": {
      "type": "string",
      "enum": [
        "general",
        "nas",
        "database",
        "virtualization"
      ],
      "default": "general",
      "description": "Primary workload type: general (mixed), nas (sequential reads/writes), database (random IO), virtualization (mixed random)"
    },
    "dedup_enabled": {
      "type": "boolean",
      "default": false,
      "description": "Whether ZFS deduplication is enabled (significantly increases RAM requirements)"
    },
    "l2arc_size_gb": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Size of L2ARC (read cache SSD) in gigabytes; requires additional RAM for index"
    }
  },
  "required": [
    "pool_size_tb"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

tcp_throughput

Calculate maximum TCP throughput using the Bandwidth-Delay Product (BDP) formula. Given link bandwidth and round-trip latency, computes the BDP (maximum in-flight data), achievable throughput with a given TCP window size, link utilization percentage, and recommended window size for full utilization. Critical for diagnosing slow transfers over high-latency links (WAN, VPN, satellite), tuning TCP buffers, and understanding why a 1Gbps link may only deliver 25Mbps with default 64KB windows. Applies to iperf testing, WAN optimization, and network capacity planning.

Parameters4

bandwidth_mbps	number	required	Available link bandwidth in megabits per second
rtt_ms	number	required	Round-trip time (latency) in milliseconds
window_size_kb	number	optional	TCP receive window size in kilobytes
mss_bytes	number	optional	Maximum Segment Size in bytes (typically 1460 for Ethernet)

Raw schema

{
  "type": "object",
  "properties": {
    "bandwidth_mbps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Available link bandwidth in megabits per second"
    },
    "rtt_ms": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Round-trip time (latency) in milliseconds"
    },
    "window_size_kb": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 64,
      "description": "TCP receive window size in kilobytes"
    },
    "mss_bytes": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1460,
      "description": "Maximum Segment Size in bytes (typically 1460 for Ethernet)"
    }
  },
  "required": [
    "bandwidth_mbps",
    "rtt_ms"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

wireguard_mtu

Calculate the optimal MTU for a WireGuard VPN tunnel interface with a detailed overhead breakdown. Accounts for WireGuard header (32 bytes), outer IP header (20 bytes IPv4 or 40 bytes IPv6), UDP header (8 bytes), and optional PPPoE encapsulation (8 bytes). Prevents fragmentation and PMTUD black holes by computing the maximum inner packet size that fits within the physical link MTU. Essential for WireGuard setup on residential ISP connections (PPPoE), IPv6 tunnels, and any VPN where incorrect MTU causes slow or stalled connections.

Parameters3

interface_mtu	integer	optional	MTU of the underlying physical or virtual network interface in bytes
ipv6	boolean	optional	Whether the outer (transport) IP header uses IPv6 (40 bytes) instead of IPv4 (20 bytes)
over_pppoe	boolean	optional	Whether the link uses PPPoE encapsulation (adds 8 bytes of overhead)

Raw schema

{
  "type": "object",
  "properties": {
    "interface_mtu": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1500,
      "description": "MTU of the underlying physical or virtual network interface in bytes"
    },
    "ipv6": {
      "type": "boolean",
      "default": false,
      "description": "Whether the outer (transport) IP header uses IPv6 (40 bytes) instead of IPv4 (20 bytes)"
    },
    "over_pppoe": {
      "type": "boolean",
      "default": false,
      "description": "Whether the link uses PPPoE encapsulation (adds 8 bytes of overhead)"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

subnet_calculator

Calculate IPv4 subnet details from CIDR notation. Parses a CIDR block (e.g. 192.168.1.0/24) and returns the network address, broadcast address, subnet mask, wildcard mask, first and last usable host addresses, total and usable host counts, prefix length, and classful IP class (A/B/C/D/E). Essential for homelab network planning, VLAN segmentation, firewall rule design, and understanding address space allocation. Handles special cases for /31 point-to-point links (RFC 3021) and /32 host routes.

Parameters1

cidr

string

required

IPv4 address in CIDR notation, e.g. 192.168.1.0/24

Raw schema

{
  "type": "object",
  "properties": {
    "cidr": {
      "type": "string",
      "pattern": "^\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\/\\d{1,2}$",
      "description": "IPv4 address in CIDR notation, e.g. 192.168.1.0/24"
    }
  },
  "required": [
    "cidr"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

raid_iops

Estimate RAID array IOPS performance and latency for ZFS and traditional RAID configurations. Calculates maximum read IOPS, write IOPS (accounting for write penalty/amplification per RAID level), blended IOPS for a configurable read/write workload mix, and rough per-disk latency. Supports stripe, mirror, raidz1, raidz2, and raidz3. Use with HDD IOPS (~150), SATA SSD (~50000), or NVMe SSD (~100000) to compare RAID topologies and plan storage performance for databases, VMs, media servers, and general homelab NAS workloads. Chains from zfs_capacity.data_disks for integrated capacity+performance planning.

Parameters4

disk_count	integer	required	Total number of physical disks in the array
disk_iops	number	optional	IOPS per individual disk. Typical values: HDD ~150, SATA SSD ~50000, NVMe SSD ~100000
raid_type	string	optional	RAID level: stripe (no redundancy, write penalty 1), mirror (write penalty 2), raidz1 (write penalty 2), raidz2 (write penalty 3), raidz3 (write penalty 4)
read_pct	number	optional	Percentage of workload that is reads (0-100). Typical: 70 for mixed, 90 for read-heavy, 30 for write-heavy

Raw schema

{
  "type": "object",
  "properties": {
    "disk_count": {
      "type": "integer",
      "minimum": 1,
      "description": "Total number of physical disks in the array"
    },
    "disk_iops": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 150,
      "description": "IOPS per individual disk. Typical values: HDD ~150, SATA SSD ~50000, NVMe SSD ~100000"
    },
    "raid_type": {
      "type": "string",
      "enum": [
        "stripe",
        "mirror",
        "raidz1",
        "raidz2",
        "raidz3"
      ],
      "default": "raidz1",
      "description": "RAID level: stripe (no redundancy, write penalty 1), mirror (write penalty 2), raidz1 (write penalty 2), raidz2 (write penalty 3), raidz3 (write penalty 4)"
    },
    "read_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 70,
      "description": "Percentage of workload that is reads (0-100). Typical: 70 for mixed, 90 for read-heavy, 30 for write-heavy"
    }
  },
  "required": [
    "disk_count"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

power_cost

Calculate total power consumption, electricity cost, and circuit requirements for a homelab. Enter each device's wattage to get daily/monthly/yearly kWh and cost at your local electricity rate. Accounts for cooling overhead via PUE (Power Usage Effectiveness). Shows amperage draw at 120V and 240V and warns if you exceed the NEC 80% continuous load limit on a 15A breaker. Essential for budgeting homelab operating expenses and ensuring your electrical panel can handle the load. Chain output total_watts into cooling_btu for heat load sizing.

Parameters4

devices	array	required	List of devices with their wattage
hours_per_day	number	optional	Hours per day the devices are running
kwh_rate_cents	number	optional	Electricity cost in cents per kilowatt-hour
pue	number	optional	Power Usage Effectiveness — ratio of total facility power to IT equipment power. 1.0 means no cooling overhead, 1.2 is typical for a home server closet, 1.5+ for poorly ventilated spaces

Raw schema

{
  "type": "object",
  "properties": {
    "devices": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Optional label for the device (e.g. 'Dell R730')"
          },
          "watts": {
            "type": "number",
            "exclusiveMinimum": 0,
            "description": "Power draw of the device in watts"
          }
        },
        "required": [
          "watts"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "List of devices with their wattage"
    },
    "hours_per_day": {
      "type": "number",
      "minimum": 0,
      "maximum": 24,
      "default": 24,
      "description": "Hours per day the devices are running"
    },
    "kwh_rate_cents": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 12,
      "description": "Electricity cost in cents per kilowatt-hour"
    },
    "pue": {
      "type": "number",
      "minimum": 1,
      "default": 1.2,
      "description": "Power Usage Effectiveness — ratio of total facility power to IT equipment power. 1.0 means no cooling overhead, 1.2 is typical for a home server closet, 1.5+ for poorly ventilated spaces"
    }
  },
  "required": [
    "devices"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

cooling_btu

Estimate the cooling load (BTU/hr) for a homelab or server closet based on equipment wattage, room dimensions, insulation quality, and solar exposure. All electrical power converts to heat — this tool calculates equipment heat output, envelope heat gain through walls, and solar gain to produce a total BTU/hr cooling requirement. Recommends AC tonnage, mini-split sizing (rounded to standard 6K BTU increments), and exhaust fan CFM for ventilation-only cooling. Use after power_cost to size cooling for your homelab room.

Parameters8

total_watts	number	required	Total power consumption in watts — all power becomes heat
room_length_ft	number	optional	Room length in feet
room_width_ft	number	optional	Room width in feet
room_height_ft	number	optional	Room ceiling height in feet
insulation	string	optional	Wall/ceiling insulation quality: poor (uninsulated garage), average (standard drywall), good (insulated interior), excellent (server room with vapor barrier)
ambient_temp_f	number	optional	Ambient temperature outside the room in degrees Fahrenheit
target_temp_f	number	optional	Desired room temperature in degrees Fahrenheit
sun_exposure	string	optional	Solar heat gain: none (interior/basement room), partial (one exterior wall with window), full (multiple sun-facing windows)

Raw schema

{
  "type": "object",
  "properties": {
    "total_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total power consumption in watts — all power becomes heat"
    },
    "room_length_ft": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 10,
      "description": "Room length in feet"
    },
    "room_width_ft": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 10,
      "description": "Room width in feet"
    },
    "room_height_ft": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 8,
      "description": "Room ceiling height in feet"
    },
    "insulation": {
      "type": "string",
      "enum": [
        "poor",
        "average",
        "good",
        "excellent"
      ],
      "default": "average",
      "description": "Wall/ceiling insulation quality: poor (uninsulated garage), average (standard drywall), good (insulated interior), excellent (server room with vapor barrier)"
    },
    "ambient_temp_f": {
      "type": "number",
      "default": 75,
      "description": "Ambient temperature outside the room in degrees Fahrenheit"
    },
    "target_temp_f": {
      "type": "number",
      "default": 72,
      "description": "Desired room temperature in degrees Fahrenheit"
    },
    "sun_exposure": {
      "type": "string",
      "enum": [
        "none",
        "partial",
        "full"
      ],
      "default": "partial",
      "description": "Solar heat gain: none (interior/basement room), partial (one exterior wall with window), full (multiple sun-facing windows)"
    }
  },
  "required": [
    "total_watts"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

rack_capacity

Quick rack space and weight sizing calculator for homelab and small data center racks. Enter your devices with their height in rack units, weight, and wattage to get total utilization, remaining free space, weight totals in lbs and kg, and recommended PDU count based on the NEC 80% continuous load rule (1920W per 20A/120V PDU). Estimates cable management overhead at 2U per 10U of installed gear. Outputs total_watts that chains into power_cost and cooling_btu for full infrastructure planning.

Parameters2

rack_units	integer	optional	Total rack height in rack units (standard is 42U)
devices	array	required	List of devices to place in the rack

Raw schema

{
  "type": "object",
  "properties": {
    "rack_units": {
      "type": "integer",
      "minimum": 1,
      "default": 42,
      "description": "Total rack height in rack units (standard is 42U)"
    },
    "devices": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Optional label for the device (e.g. 'Dell R730', 'Patch Panel')"
          },
          "height_u": {
            "type": "integer",
            "minimum": 1,
            "maximum": 10,
            "description": "Height of the device in rack units (U)"
          },
          "weight_lbs": {
            "type": "number",
            "minimum": 0,
            "default": 0,
            "description": "Weight of the device in pounds"
          },
          "watts": {
            "type": "number",
            "minimum": 0,
            "default": 0,
            "description": "Power draw of the device in watts"
          }
        },
        "required": [
          "height_u"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "List of devices to place in the rack"
    }
  },
  "required": [
    "devices"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

network_bandwidth

Plan and validate network link capacity for homelab workloads. Determine whether a 1G, 2.5G, 10G, or faster link can handle your concurrent streams (VMs, backups, media, iSCSI). Calculates effective bandwidth after TCP/IP overhead, total required bandwidth, utilization percentage, and remaining headroom. Flags saturation at 80% utilization and identifies whether the bottleneck is network or storage. Provides a 1TB transfer time reference and recommends the next link speed upgrade if your current link is saturated. Useful for planning NIC upgrades, switch purchases, and storage network design.

Parameters5

link_speed_gbps	number	required	Network link speed in gigabits per second (e.g. 1, 2.5, 5, 10, 25, 40, 100)
concurrent_streams	integer	optional	Number of concurrent data streams / transfers
stream_bandwidth_mbps	number	optional	Bandwidth required per stream in megabits per second
protocol_overhead_pct	number	optional	TCP/IP protocol overhead as a percentage (typically 3-5% for TCP, ~1% for UDP)
storage_throughput_mbps	number	optional	Maximum storage read/write throughput in megabits per second. If provided, checks whether storage is the bottleneck

Raw schema

{
  "type": "object",
  "properties": {
    "link_speed_gbps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Network link speed in gigabits per second (e.g. 1, 2.5, 5, 10, 25, 40, 100)"
    },
    "concurrent_streams": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Number of concurrent data streams / transfers"
    },
    "stream_bandwidth_mbps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 100,
      "description": "Bandwidth required per stream in megabits per second"
    },
    "protocol_overhead_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 50,
      "default": 3,
      "description": "TCP/IP protocol overhead as a percentage (typically 3-5% for TCP, ~1% for UDP)"
    },
    "storage_throughput_mbps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Maximum storage read/write throughput in megabits per second. If provided, checks whether storage is the bottleneck"
    }
  },
  "required": [
    "link_speed_gbps"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

thermal_enclosure

Estimate steady-state thermal behaviour of a rectangular enclosure (server rack, electronics housing, equipment cabinet) using a lumped-parameter energy balance with natural-convection and radiation correlations, or forced-flow air energy balance. Accepts enclosure dimensions, heat source positions and wattages, and airflow configuration. Returns temperature extremes, estimated hotspot location, airflow velocity summary, and overall thermal resistance. Runs instantly in-worker; a full CFD container backend is planned for mesh-level detail.

Parameters10

length_m	number	required	Enclosure length (X) in metres
width_m	number	required	Enclosure width (Y) in metres
height_m	number	required	Enclosure height (Z) in metres
heat_sources	array	required	Heat sources inside the enclosure
flow_type	string	required	Airflow type
inlet_velocity_ms	number	optional	Inlet air velocity in m/s (required for forced flow)
inlet_position	string	optional	Inlet location
outlet_position	string	optional	Outlet location
ambient_temp_c	number	optional	Ambient air temperature in Celsius
mesh_density	string	optional	Mesh density — coarse (~50K cells), medium (~200K), fine (~500K)

Raw schema

{
  "type": "object",
  "properties": {
    "length_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 2,
      "description": "Enclosure length (X) in metres"
    },
    "width_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 2,
      "description": "Enclosure width (Y) in metres"
    },
    "height_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 2,
      "description": "Enclosure height (Z) in metres"
    },
    "heat_sources": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "x_m": {
            "type": "number",
            "minimum": 0,
            "description": "X position in metres from enclosure origin"
          },
          "y_m": {
            "type": "number",
            "minimum": 0,
            "description": "Y position in metres"
          },
          "z_m": {
            "type": "number",
            "minimum": 0,
            "description": "Z position in metres"
          },
          "watts": {
            "type": "number",
            "exclusiveMinimum": 0,
            "description": "Heat dissipation in watts"
          },
          "label": {
            "type": "string",
            "description": "Optional label (e.g. 'CPU', 'PSU')"
          }
        },
        "required": [
          "x_m",
          "y_m",
          "z_m",
          "watts"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "Heat sources inside the enclosure"
    },
    "flow_type": {
      "type": "string",
      "enum": [
        "natural_convection",
        "forced"
      ],
      "description": "Airflow type"
    },
    "inlet_velocity_ms": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Inlet air velocity in m/s (required for forced flow)"
    },
    "inlet_position": {
      "type": "string",
      "enum": [
        "front_bottom",
        "front_center",
        "side_bottom"
      ],
      "default": "front_bottom",
      "description": "Inlet location"
    },
    "outlet_position": {
      "type": "string",
      "enum": [
        "rear_top",
        "rear_center",
        "top_rear"
      ],
      "default": "rear_top",
      "description": "Outlet location"
    },
    "ambient_temp_c": {
      "type": "number",
      "default": 25,
      "description": "Ambient air temperature in Celsius"
    },
    "mesh_density": {
      "type": "string",
      "enum": [
        "coarse",
        "medium",
        "fine"
      ],
      "default": "medium",
      "description": "Mesh density — coarse (~50K cells), medium (~200K), fine (~500K)"
    }
  },
  "required": [
    "length_m",
    "width_m",
    "height_m",
    "heat_sources",
    "flow_type"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

heatsink_cfd

Analyze a forced-convection fin-array heatsink using established channel-flow correlations (developing laminar Nusselt, fin efficiency tanh(mH)/mH, parallel-plate friction). Computes base-to-air thermal resistance, pressure drop, base and fin-tip temperatures, fin efficiency, and the optimal fin spacing for the given airflow. Use for heatsink selection and first-pass optimization in electronics cooling. Runs instantly in-worker; mesh-level CFD via container backend is planned.

Parameters10

base_length_m	number	required	Heatsink base length in metres
base_width_m	number	required	Heatsink base width in metres
base_height_m	number	required	Base plate thickness in metres
fin_count	integer	required	Number of fins
fin_height_m	number	required	Fin height in metres
fin_thickness_m	number	required	Fin thickness in metres
airflow_velocity_ms	number	required	Incoming airflow velocity in m/s
heat_load_w	number	required	Total heat load applied to base in watts
ambient_temp_c	number	optional	Ambient air temperature in Celsius
mesh_density	string	optional	Mesh density

Raw schema

{
  "type": "object",
  "properties": {
    "base_length_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.5,
      "description": "Heatsink base length in metres"
    },
    "base_width_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.5,
      "description": "Heatsink base width in metres"
    },
    "base_height_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.05,
      "description": "Base plate thickness in metres"
    },
    "fin_count": {
      "type": "integer",
      "minimum": 2,
      "maximum": 100,
      "description": "Number of fins"
    },
    "fin_height_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.2,
      "description": "Fin height in metres"
    },
    "fin_thickness_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.01,
      "description": "Fin thickness in metres"
    },
    "airflow_velocity_ms": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 20,
      "description": "Incoming airflow velocity in m/s"
    },
    "heat_load_w": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total heat load applied to base in watts"
    },
    "ambient_temp_c": {
      "type": "number",
      "default": 25,
      "description": "Ambient air temperature in Celsius"
    },
    "mesh_density": {
      "type": "string",
      "enum": [
        "coarse",
        "medium",
        "fine"
      ],
      "default": "medium",
      "description": "Mesh density"
    }
  },
  "required": [
    "base_length_m",
    "base_width_m",
    "base_height_m",
    "fin_count",
    "fin_height_m",
    "fin_thickness_m",
    "airflow_velocity_ms",
    "heat_load_w"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

pcb_thermal

Estimate PCB component temperatures by solving a thermal resistance network (thermal↔electrical analogy) with the built-in MNA solver. Each component gets a junction node (package θjb from a typical-datasheet table), a local board node coupled to its neighbours through in-plane FR4/copper conduction, and convection to ambient. Computes per-component junction and case temperatures, board extremes, and flags max-junction violations. Runs instantly in-worker; mesh-level CFD via container backend is planned.

Parameters7

board_length_m	number	required	Board length in metres
board_width_m	number	required	Board width in metres
board_thickness_m	number	optional	Board thickness in metres (default 1.6mm FR4)
components	array	required	Components on the board
airflow_velocity_ms	number	optional	Airflow velocity in m/s (0 = natural convection)
ambient_temp_c	number	optional	Ambient temperature in Celsius
mesh_density	string	optional	Mesh density

Raw schema

{
  "type": "object",
  "properties": {
    "board_length_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.5,
      "description": "Board length in metres"
    },
    "board_width_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 0.5,
      "description": "Board width in metres"
    },
    "board_thickness_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 0.0016,
      "description": "Board thickness in metres (default 1.6mm FR4)"
    },
    "components": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "x_m": {
            "type": "number",
            "minimum": 0,
            "description": "X position on board in metres"
          },
          "y_m": {
            "type": "number",
            "minimum": 0,
            "description": "Y position on board in metres"
          },
          "footprint": {
            "type": "string",
            "description": "Package footprint (e.g. QFP-48, BGA-256, SOT-23, TO-220)"
          },
          "tdp_w": {
            "type": "number",
            "exclusiveMinimum": 0,
            "description": "Thermal design power in watts"
          },
          "label": {
            "type": "string",
            "description": "Component label (e.g. 'U1', 'CPU')"
          },
          "max_junction_temp_c": {
            "type": "number",
            "description": "Maximum junction temperature (°C) for violation checking"
          }
        },
        "required": [
          "x_m",
          "y_m",
          "footprint",
          "tdp_w"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "Components on the board"
    },
    "airflow_velocity_ms": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Airflow velocity in m/s (0 = natural convection)"
    },
    "ambient_temp_c": {
      "type": "number",
      "default": 25,
      "description": "Ambient temperature in Celsius"
    },
    "mesh_density": {
      "type": "string",
      "enum": [
        "coarse",
        "medium",
        "fine"
      ],
      "default": "medium",
      "description": "Mesh density"
    }
  },
  "required": [
    "board_length_m",
    "board_width_m",
    "components"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

battery_life

Calculates battery runtime and energy capacity given cell capacity in mAh, nominal voltage, and average current draw. Accounts for real-world discharge efficiency (Peukert-adjacent derating) to produce effective capacity, total energy in Wh, and runtime in hours and days. Useful for IoT sensor node planning, portable device design, UPS hold-up estimation, and solar battery bank cycling analysis. Outputs feed into solar_sizing (battery_kwh) and ups_runtime (battery_wh) for system-level calculations.

Parameters4

capacity_mah	number	required	Battery capacity in milliamp-hours (mAh)
voltage	number	optional	Nominal battery voltage (V), default 3.7 for Li-ion
current_draw_ma	number	required	Average current draw in milliamps (mA)
efficiency	number	optional	Discharge efficiency factor (0-1), accounts for conversion losses and derating, default 0.85

Raw schema

{
  "type": "object",
  "properties": {
    "capacity_mah": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Battery capacity in milliamp-hours (mAh)"
    },
    "voltage": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3.7,
      "description": "Nominal battery voltage (V), default 3.7 for Li-ion"
    },
    "current_draw_ma": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Average current draw in milliamps (mA)"
    },
    "efficiency": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.85,
      "description": "Discharge efficiency factor (0-1), accounts for conversion losses and derating, default 0.85"
    }
  },
  "required": [
    "capacity_mah",
    "current_draw_ma"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

wire_gauge

Determines the minimum AWG (American Wire Gauge) conductor size for a given current, voltage, one-way cable distance, and maximum allowable voltage drop percentage. Supports copper and aluminum conductors. Computes round-trip resistance, actual voltage drop in volts and percent, and wire cross-sectional area. Essential for DC solar runs, battery bank wiring, EV charging circuits, and low-voltage landscape lighting. NEC recommends 3% max drop for branch circuits and 5% total including feeder. Outputs the smallest AWG that satisfies the drop constraint.

Parameters5

current_amps	number	required	Load current in amperes (A)
voltage	number	required	System voltage (V)
distance_m	number	required	One-way conductor distance in meters
max_drop_pct	number	optional	Maximum allowable voltage drop as percentage (default 3%)
conductor	string	optional	Conductor material: copper or aluminum

Raw schema

{
  "type": "object",
  "properties": {
    "current_amps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Load current in amperes (A)"
    },
    "voltage": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "System voltage (V)"
    },
    "distance_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "One-way conductor distance in meters"
    },
    "max_drop_pct": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3,
      "description": "Maximum allowable voltage drop as percentage (default 3%)"
    },
    "conductor": {
      "type": "string",
      "enum": [
        "copper",
        "aluminum"
      ],
      "default": "copper",
      "description": "Conductor material: copper or aluminum"
    }
  },
  "required": [
    "current_amps",
    "voltage",
    "distance_m"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

solar_sizing

Sizes an off-grid solar power system by calculating the number of panels and battery bank capacity required for a given daily energy consumption. Accounts for system losses (inverter, wiring, charge controller), battery depth-of-discharge, and autonomy days for cloudy weather. Outputs panel count, total panel wattage, battery capacity in kWh and Ah, and minimum charge controller amperage (with 25% safety margin per NEC 690.8). Supports 12V, 24V, and 48V system architectures. Use for cabin, RV, telecom tower, and remote IoT deployments.

Parameters7

daily_kwh	number	required	Daily energy consumption in kilowatt-hours (kWh)
peak_sun_hours	number	optional	Average peak sun hours per day for your location (hours)
panel_watts	number	optional	Rated wattage per solar panel (W)
system_voltage	number	optional	Battery bank system voltage: 12, 24, or 48 V
battery_autonomy_days	number	optional	Number of days the battery bank should sustain load without solar input
dod	number	optional	Battery depth of discharge (0-1), default 0.8 for LiFePO4
system_efficiency	number	optional	Overall system efficiency (0-1), accounts for inverter, wiring, and controller losses

Raw schema

{
  "type": "object",
  "properties": {
    "daily_kwh": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Daily energy consumption in kilowatt-hours (kWh)"
    },
    "peak_sun_hours": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 5,
      "description": "Average peak sun hours per day for your location (hours)"
    },
    "panel_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 400,
      "description": "Rated wattage per solar panel (W)"
    },
    "system_voltage": {
      "type": "number",
      "enum": [
        12,
        24,
        48
      ],
      "default": 48,
      "description": "Battery bank system voltage: 12, 24, or 48 V"
    },
    "battery_autonomy_days": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 2,
      "description": "Number of days the battery bank should sustain load without solar input"
    },
    "dod": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.8,
      "description": "Battery depth of discharge (0-1), default 0.8 for LiFePO4"
    },
    "system_efficiency": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.85,
      "description": "Overall system efficiency (0-1), accounts for inverter, wiring, and controller losses"
    }
  },
  "required": [
    "daily_kwh"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

ups_runtime

Estimates UPS (Uninterruptible Power Supply) backup runtime from battery specifications and connected load. Takes VA rating, watt rating, load in watts, and battery configuration (count, voltage, amp-hours) to compute effective stored energy after efficiency losses and runtime in minutes and hours. Detects overload conditions when load exceeds the UPS watt rating. Calculates power factor from VA/W ratings. Ideal for server rack planning, homelab power budgeting, network closet UPS selection, and graceful shutdown timer configuration.

Parameters7

va_rating	number	required	UPS VA (volt-ampere) rating
watt_rating	number	required	UPS real power (watt) rating
load_watts	number	required	Connected load in watts
battery_count	integer	optional	Number of batteries in the UPS
battery_voltage	number	optional	Voltage per battery (V)
battery_ah	number	optional	Capacity per battery in amp-hours (Ah)
efficiency	number	optional	Inverter/conversion efficiency (0-1), default 0.9

Raw schema

{
  "type": "object",
  "properties": {
    "va_rating": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "UPS VA (volt-ampere) rating"
    },
    "watt_rating": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "UPS real power (watt) rating"
    },
    "load_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Connected load in watts"
    },
    "battery_count": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Number of batteries in the UPS"
    },
    "battery_voltage": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 12,
      "description": "Voltage per battery (V)"
    },
    "battery_ah": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 9,
      "description": "Capacity per battery in amp-hours (Ah)"
    },
    "efficiency": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.9,
      "description": "Inverter/conversion efficiency (0-1), default 0.9"
    }
  },
  "required": [
    "va_rating",
    "watt_rating",
    "load_watts"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

mah_to_wh

Converts battery capacity from milliamp-hours (mAh) to watt-hours (Wh), kilowatt-hours (kWh), and joules (J) given the nominal cell voltage. This is the most common battery unit conversion needed when comparing cells rated in mAh (e.g. 18650, AA) against energy budgets specified in Wh. Essential for airline lithium battery compliance (100 Wh limit for carry-on), solar battery bank sizing, and UPS capacity planning. Echoes back input values for easy chaining into battery_life, solar_sizing, and ups_runtime tools.

Parameters2

capacity_mah	number	required	Battery capacity in milliamp-hours (mAh)
voltage_v	number	required	Nominal battery voltage (V)

Raw schema

{
  "type": "object",
  "properties": {
    "capacity_mah": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Battery capacity in milliamp-hours (mAh)"
    },
    "voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Nominal battery voltage (V)"
    }
  },
  "required": [
    "capacity_mah",
    "voltage_v"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

watts_to_amps

Converts electrical power in watts to current in amps (and milliamps) for a given voltage, using the DC power formula P = V * I. Also computes the implied load resistance via Ohm's law (R = V / I) assuming a purely resistive load. This is the most common electrical conversion for circuit design, fuse selection, wire sizing, and breaker rating. Use the output amps value to feed into wire_gauge for conductor sizing or voltage_drop for cable loss analysis. Covers DC circuits; for AC with power factor, adjust watts to true power first.

Parameters2

watts	number	required	Power in watts (W)
voltage_v	number	required	Voltage in volts (V)

Raw schema

{
  "type": "object",
  "properties": {
    "watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Power in watts (W)"
    },
    "voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Voltage in volts (V)"
    }
  },
  "required": [
    "watts",
    "voltage_v"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

voltage_drop

Calculates voltage drop across a conductor run given current, wire length, AWG gauge, system voltage, and conductor material (copper or aluminum). Computes round-trip resistance, voltage drop in volts and percent, voltage at the load end, power dissipated in the wire, and NEC compliance flags (3% max for branch circuits, 5% max for feeders). Use this after wire_gauge to verify a specific gauge meets requirements, or to evaluate an existing installation. Critical for solar panel string wiring, EV charger circuits, low-voltage lighting, and any long DC or AC cable run where resistive losses matter.

Parameters5

current_amps	number	required	Load current in amperes (A)
wire_length_m	number	required	One-way wire length in meters
wire_gauge_awg	number	required	Wire gauge in AWG (e.g. 14, 12, 10; use negative for large gauges: -3 = 4/0)
voltage_v	number	required	System voltage (V)
conductor	string	optional	Conductor material: copper or aluminum

Raw schema

{
  "type": "object",
  "properties": {
    "current_amps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Load current in amperes (A)"
    },
    "wire_length_m": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "One-way wire length in meters"
    },
    "wire_gauge_awg": {
      "type": "number",
      "description": "Wire gauge in AWG (e.g. 14, 12, 10; use negative for large gauges: -3 = 4/0)"
    },
    "voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "System voltage (V)"
    },
    "conductor": {
      "type": "string",
      "enum": [
        "copper",
        "aluminum"
      ],
      "default": "copper",
      "description": "Conductor material: copper or aluminum"
    }
  },
  "required": [
    "current_amps",
    "wire_length_m",
    "wire_gauge_awg",
    "voltage_v"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

battery_charge_time

Estimates battery charge time given capacity in mAh, charge current in mA, charger efficiency, and initial state of charge. Accounts for real-world charging losses (typically 80-90% efficient) to produce time in hours and minutes, energy required in Wh (at an optional voltage, default 3.7V for Li-ion), and the C-rate of the charge. Useful for solar charge controller sizing, USB charging time estimation, lead-acid float charging, and EV battery planning. The C-rate output helps verify the charge current is within safe limits (typically 0.5C-1C for Li-ion). Chain from solar_sizing charge_controller_amps to size a solar charging system end-to-end.

Parameters5

capacity_mah	number	required	Total battery capacity in milliamp-hours (mAh)
charge_current_ma	number	required	Charge current in milliamps (mA)
efficiency	number	optional	Charger efficiency factor (0-1), default 0.85
initial_soc_pct	number	optional	Initial state of charge as percentage (0-100), default 0 (empty)
voltage_v	number	optional	Nominal battery voltage for energy calculation (V), default 3.7 for Li-ion

Raw schema

{
  "type": "object",
  "properties": {
    "capacity_mah": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total battery capacity in milliamp-hours (mAh)"
    },
    "charge_current_ma": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Charge current in milliamps (mA)"
    },
    "efficiency": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.85,
      "description": "Charger efficiency factor (0-1), default 0.85"
    },
    "initial_soc_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 0,
      "description": "Initial state of charge as percentage (0-100), default 0 (empty)"
    },
    "voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3.7,
      "description": "Nominal battery voltage for energy calculation (V), default 3.7 for Li-ion"
    }
  },
  "required": [
    "capacity_mah",
    "charge_current_ma"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

solar_load_audit

Calculates total daily energy consumption from an appliance list — the critical first step before sizing solar panels or batteries. Enter each appliance with its wattage, hours of daily use, and quantity. Outputs total daily kWh (with configurable safety margin for surge and inrush current), peak simultaneous wattage, and recommended inverter VA rating per NEC 125% continuous load rule. Feeds directly into solar_sizing (daily_kwh) and battery_autonomy (daily_kwh). Essential for residential, RV, cabin, and off-grid system design.

Parameters2

appliances	array	required	List of appliances with wattage, hours per day, and quantity
safety_margin_pct	number	optional	Safety margin percentage to account for surge/inrush current, default 20%

Raw schema

{
  "type": "object",
  "properties": {
    "appliances": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Appliance name (e.g. 'Refrigerator', 'LED Light')"
          },
          "watts": {
            "type": "number",
            "exclusiveMinimum": 0,
            "description": "Power consumption in watts (W)"
          },
          "hours_per_day": {
            "type": "number",
            "minimum": 0,
            "maximum": 24,
            "description": "Average hours of use per day"
          },
          "quantity": {
            "type": "integer",
            "exclusiveMinimum": 0,
            "default": 1,
            "description": "Number of identical units, default 1"
          }
        },
        "required": [
          "name",
          "watts",
          "hours_per_day"
        ],
        "additionalProperties": false
      },
      "minItems": 1,
      "description": "List of appliances with wattage, hours per day, and quantity"
    },
    "safety_margin_pct": {
      "type": "number",
      "minimum": 0,
      "default": 20,
      "description": "Safety margin percentage to account for surge/inrush current, default 20%"
    }
  },
  "required": [
    "appliances"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

solar_roi

Calculates solar system return on investment, payback period, and levelized cost of energy (LCOE). Models year-by-year savings accounting for panel degradation, utility rate inflation, federal Investment Tax Credit (ITC), state rebates, and annual maintenance. Outputs net cost after incentives, payback year, total lifetime savings, ROI percentage, and LCOE in cents/kWh. Essential for residential and commercial solar financial analysis, installer proposals, and comparing solar vs. grid economics over a 25-year system lifetime.

Parameters10

system_cost_usd	number	required	Total installed system cost in USD
system_size_kw	number	required	System size in kilowatts (kW)
annual_production_kwh	number	required	Estimated annual energy production in kWh (from PVWatts or system_size_kw * peak_sun_hours * 365 * 0.80)
electricity_rate_cents	number	optional	Current electricity rate in cents per kWh, default 15
annual_rate_increase_pct	number	optional	Annual utility rate increase percentage, default 3%
federal_itc_pct	number	optional	Federal Investment Tax Credit percentage, default 30% (US ITC)
state_rebate_usd	number	optional	State or local rebate amount in USD, default 0
annual_degradation_pct	number	optional	Annual panel degradation rate, default 0.5% per year
annual_maintenance_usd	number	optional	Annual maintenance cost in USD, default $100
system_lifetime_years	integer	optional	System lifetime in years, default 25

Raw schema

{
  "type": "object",
  "properties": {
    "system_cost_usd": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total installed system cost in USD"
    },
    "system_size_kw": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "System size in kilowatts (kW)"
    },
    "annual_production_kwh": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Estimated annual energy production in kWh (from PVWatts or system_size_kw * peak_sun_hours * 365 * 0.80)"
    },
    "electricity_rate_cents": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 15,
      "description": "Current electricity rate in cents per kWh, default 15"
    },
    "annual_rate_increase_pct": {
      "type": "number",
      "minimum": 0,
      "default": 3,
      "description": "Annual utility rate increase percentage, default 3%"
    },
    "federal_itc_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 30,
      "description": "Federal Investment Tax Credit percentage, default 30% (US ITC)"
    },
    "state_rebate_usd": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "State or local rebate amount in USD, default 0"
    },
    "annual_degradation_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 5,
      "default": 0.5,
      "description": "Annual panel degradation rate, default 0.5% per year"
    },
    "annual_maintenance_usd": {
      "type": "number",
      "minimum": 0,
      "default": 100,
      "description": "Annual maintenance cost in USD, default $100"
    },
    "system_lifetime_years": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 25,
      "description": "System lifetime in years, default 25"
    }
  },
  "required": [
    "system_cost_usd",
    "system_size_kw",
    "annual_production_kwh"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

battery_autonomy

Calculates how many days a battery bank can sustain loads without solar input — critical for off-grid and backup power sizing. Accounts for depth of discharge, round-trip efficiency (lithium vs lead-acid), minimum state of charge, and optional partial solar contribution during cloudy weather. Outputs autonomy in days and hours, usable capacity, and daily deficit. Use with avg_solar_contribution_pct = 0 for worst-case (no sun) scenarios, or 20-30% for realistic cloudy-day modeling. Chains from solar_sizing (battery_kwh) and solar_load_audit (daily_kwh).

Parameters6

daily_kwh	number	required	Daily energy consumption in kilowatt-hours (kWh)
battery_kwh	number	required	Total installed battery capacity in kWh
dod	number	optional	Depth of discharge (0-1), default 0.8 for lithium
round_trip_efficiency	number	optional	Battery round-trip efficiency (0-1), default 0.90 for lithium, use 0.80 for lead-acid
min_soc_pct	number	optional	Minimum state of charge percentage, default 20%
avg_solar_contribution_pct	number	optional	Average solar contribution during autonomy period (0-100%), default 0 for worst-case

Raw schema

{
  "type": "object",
  "properties": {
    "daily_kwh": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Daily energy consumption in kilowatt-hours (kWh)"
    },
    "battery_kwh": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total installed battery capacity in kWh"
    },
    "dod": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.8,
      "description": "Depth of discharge (0-1), default 0.8 for lithium"
    },
    "round_trip_efficiency": {
      "type": "number",
      "minimum": 0,
      "maximum": 1,
      "default": 0.9,
      "description": "Battery round-trip efficiency (0-1), default 0.90 for lithium, use 0.80 for lead-acid"
    },
    "min_soc_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 20,
      "description": "Minimum state of charge percentage, default 20%"
    },
    "avg_solar_contribution_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 0,
      "description": "Average solar contribution during autonomy period (0-100%), default 0 for worst-case"
    }
  },
  "required": [
    "daily_kwh",
    "battery_kwh"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

string_sizing

Calculates optimal solar panel string and MPPT configuration based on panel electrical specs, inverter/charge-controller MPPT limits, and site temperature extremes. Applies temperature coefficients to determine Voc at minimum temperature (cold) and Vmp at maximum temperature (hot), then computes the safe range of panels per string, maximum parallel strings, and total array wattage. Prevents over-voltage damage in winter and under-voltage MPPT dropout in summer. Essential for NEC 690.7 compliant residential and commercial solar design.

Parameters10

panel_voc	number	required	Panel open circuit voltage (Voc) at STC in volts
panel_vmp	number	required	Panel maximum power voltage (Vmp) at STC in volts
panel_isc	number	required	Panel short circuit current (Isc) at STC in amps
panel_imp	number	required	Panel maximum power current (Imp) at STC in amps
mppt_vmax	number	required	Maximum MPPT input voltage in volts
mppt_vmin	number	required	Minimum MPPT start/operating voltage in volts
mppt_imax	number	required	Maximum MPPT input current in amps
temp_min_c	number	optional	Minimum expected site temperature in Celsius, default -10
temp_max_c	number	optional	Maximum expected cell temperature in Celsius, default 60
temp_coeff_voc_pct_per_c	number	optional	Voc temperature coefficient in %/C (negative for silicon), default -0.30

Raw schema

{
  "type": "object",
  "properties": {
    "panel_voc": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Panel open circuit voltage (Voc) at STC in volts"
    },
    "panel_vmp": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Panel maximum power voltage (Vmp) at STC in volts"
    },
    "panel_isc": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Panel short circuit current (Isc) at STC in amps"
    },
    "panel_imp": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Panel maximum power current (Imp) at STC in amps"
    },
    "mppt_vmax": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Maximum MPPT input voltage in volts"
    },
    "mppt_vmin": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Minimum MPPT start/operating voltage in volts"
    },
    "mppt_imax": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Maximum MPPT input current in amps"
    },
    "temp_min_c": {
      "type": "number",
      "default": -10,
      "description": "Minimum expected site temperature in Celsius, default -10"
    },
    "temp_max_c": {
      "type": "number",
      "default": 60,
      "description": "Maximum expected cell temperature in Celsius, default 60"
    },
    "temp_coeff_voc_pct_per_c": {
      "type": "number",
      "default": -0.3,
      "description": "Voc temperature coefficient in %/C (negative for silicon), default -0.30"
    }
  },
  "required": [
    "panel_voc",
    "panel_vmp",
    "panel_isc",
    "panel_imp",
    "mppt_vmax",
    "mppt_vmin",
    "mppt_imax"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

generator_offset

Compares total cost of ownership between a fuel generator and a solar+battery system over a configurable time horizon. Calculates yearly and cumulative costs for generator-only, solar-only (amortized), and hybrid scenarios. Accounts for fuel cost, generator consumption rate, maintenance intervals, solar system amortization, and battery coverage. Outputs yearly costs, total savings, breakeven year, solar coverage percentage, and generator hours saved. Essential for off-grid site planning, remote telecom towers, construction sites, and rural electrification proposals.

Parameters9

generator_fuel_cost_per_gallon	number	optional	Fuel cost per gallon in USD, default $3.50
generator_consumption_gph	number	optional	Generator fuel consumption in gallons per hour at load, default 1.0
generator_hours_per_day	number	optional	Generator runtime hours per day, default 8
generator_maintenance_per_1000hrs	number	optional	Generator maintenance cost per 1000 running hours in USD, default $200
solar_system_cost_usd	number	required	Total solar+battery system cost in USD
solar_daily_kwh_produced	number	required	Daily solar energy production in kWh
battery_kwh	number	optional	Battery storage capacity in kWh (0 means no battery, generator needed at night), default 0
daily_kwh_needed	number	required	Total daily energy requirement in kWh
years_to_compare	integer	optional	Number of years to compare, default 10

Raw schema

{
  "type": "object",
  "properties": {
    "generator_fuel_cost_per_gallon": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 3.5,
      "description": "Fuel cost per gallon in USD, default $3.50"
    },
    "generator_consumption_gph": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Generator fuel consumption in gallons per hour at load, default 1.0"
    },
    "generator_hours_per_day": {
      "type": "number",
      "minimum": 0,
      "maximum": 24,
      "default": 8,
      "description": "Generator runtime hours per day, default 8"
    },
    "generator_maintenance_per_1000hrs": {
      "type": "number",
      "minimum": 0,
      "default": 200,
      "description": "Generator maintenance cost per 1000 running hours in USD, default $200"
    },
    "solar_system_cost_usd": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total solar+battery system cost in USD"
    },
    "solar_daily_kwh_produced": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Daily solar energy production in kWh"
    },
    "battery_kwh": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Battery storage capacity in kWh (0 means no battery, generator needed at night), default 0"
    },
    "daily_kwh_needed": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total daily energy requirement in kWh"
    },
    "years_to_compare": {
      "type": "integer",
      "minimum": 1,
      "maximum": 30,
      "default": 10,
      "description": "Number of years to compare, default 10"
    }
  },
  "required": [
    "solar_system_cost_usd",
    "solar_daily_kwh_produced",
    "daily_kwh_needed"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

wire_ampacity

Determine minimum wire gauge using NEC Table 310.16 ampacity ratings with full derating. Looks up base ampacity for copper or aluminum conductors at 60°C, 75°C, or 90°C insulation rating, then applies NEC 310.15(C)(1) ambient temperature correction and NEC 310.15(C)(2) conductor count adjustment. Automatically applies the 125% continuous load factor per NEC 210.20(A) when flagged. Returns the minimum AWG that meets the derated requirement, plus a comparison table of all gauges. Different from wire_gauge which focuses on voltage drop — use both together for complete wire sizing. Essential for residential panels, commercial feeders, solar arrays, and EV charging installations.

Parameters6

current_amps	number	required	Required circuit current in amperes. Use 125% of continuous load per NEC 210.20(A).
conductor	string	optional	Conductor material. Copper has higher ampacity; aluminum is lighter and cheaper for large feeders.
insulation	string	optional	Insulation temperature rating in °C. 60=TW/UF-B, 75=THW/THWN/XHHW (most common), 90=THHN/THWN-2.
ambient_temp_c	number	optional	Ambient temperature in °C. NEC base is 30°C. Higher temps require derating. Typical: 30 (indoor), 40 (attic/hot), 45+ (rooftop conduit).
conductors_in_raceway	integer	optional	Number of current-carrying conductors in a single raceway or cable. More than 3 requires derating per NEC 310.15(C)(2).
continuous_load	boolean	optional	Whether the load operates continuously (3+ hours). NEC requires 125% sizing for continuous loads. Set false for intermittent loads.

Raw schema

{
  "type": "object",
  "properties": {
    "current_amps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Required circuit current in amperes. Use 125% of continuous load per NEC 210.20(A)."
    },
    "conductor": {
      "type": "string",
      "enum": [
        "copper",
        "aluminum"
      ],
      "default": "copper",
      "description": "Conductor material. Copper has higher ampacity; aluminum is lighter and cheaper for large feeders."
    },
    "insulation": {
      "type": "string",
      "enum": [
        "60",
        "75",
        "90"
      ],
      "default": "75",
      "description": "Insulation temperature rating in °C. 60=TW/UF-B, 75=THW/THWN/XHHW (most common), 90=THHN/THWN-2."
    },
    "ambient_temp_c": {
      "type": "number",
      "default": 30,
      "description": "Ambient temperature in °C. NEC base is 30°C. Higher temps require derating. Typical: 30 (indoor), 40 (attic/hot), 45+ (rooftop conduit)."
    },
    "conductors_in_raceway": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 3,
      "description": "Number of current-carrying conductors in a single raceway or cable. More than 3 requires derating per NEC 310.15(C)(2)."
    },
    "continuous_load": {
      "type": "boolean",
      "default": true,
      "description": "Whether the load operates continuously (3+ hours). NEC requires 125% sizing for continuous loads. Set false for intermittent loads."
    }
  },
  "required": [
    "current_amps"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

inverter_sizing

Size a DC-to-AC inverter for off-grid solar, battery backup, or mobile power systems. Computes the required continuous VA rating from total load watts and power factor, estimates surge capacity for motor-starting loads (3-7x rated power), applies NEC-recommended 20% derating for continuous operation, and selects the nearest standard inverter size. Also calculates DC input current at the system voltage for cable and fuse sizing. Chain from solar_load_audit to get peak_watts and largest_load_watts, then chain to wire_gauge or wire_ampacity to size the DC cables. Essential for off-grid cabins, RV/van builds, emergency backup, and solar+battery installations.

Parameters7

continuous_watts	number	required	Total continuous load in watts. Sum of all appliances that may run simultaneously. Chain from solar_load_audit.peak_watts.
surge_watts	number	optional	Peak surge/starting load in watts. Motors and compressors draw 3-7x rated watts on startup. If omitted, estimated as 3x the largest single load or 2x continuous, whichever is greater.
largest_load_watts	number	optional	Wattage of the single largest appliance. Used to estimate surge if surge_watts is not provided. Chain from solar_load_audit.largest_load_watts.
system_voltage	string	optional	DC system voltage. 12V for small/mobile, 24V for medium, 48V for large residential/commercial. Higher voltage = lower current = thinner cables.
power_factor	number	optional	Power factor (0.5-1.0). Resistive loads (heaters, lights) are ~1.0. Motor loads (fridge, AC, pump) are 0.6-0.8. Mixed loads typically 0.8.
efficiency	number	optional	Inverter efficiency (0.5-1.0). Good pure-sine inverters are 0.90-0.95. Modified-sine are 0.85-0.90. Budget units may be lower.
derating_pct	number	optional	Derating percentage for temperature, altitude, and safety margin. NEC recommends 20% (80% continuous rating). Range 0-50%.

Raw schema

{
  "type": "object",
  "properties": {
    "continuous_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total continuous load in watts. Sum of all appliances that may run simultaneously. Chain from solar_load_audit.peak_watts."
    },
    "surge_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Peak surge/starting load in watts. Motors and compressors draw 3-7x rated watts on startup. If omitted, estimated as 3x the largest single load or 2x continuous, whichever is greater."
    },
    "largest_load_watts": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Wattage of the single largest appliance. Used to estimate surge if surge_watts is not provided. Chain from solar_load_audit.largest_load_watts."
    },
    "system_voltage": {
      "type": "string",
      "enum": [
        "12",
        "24",
        "48"
      ],
      "default": "48",
      "description": "DC system voltage. 12V for small/mobile, 24V for medium, 48V for large residential/commercial. Higher voltage = lower current = thinner cables."
    },
    "power_factor": {
      "type": "number",
      "minimum": 0.5,
      "maximum": 1,
      "default": 0.8,
      "description": "Power factor (0.5-1.0). Resistive loads (heaters, lights) are ~1.0. Motor loads (fridge, AC, pump) are 0.6-0.8. Mixed loads typically 0.8."
    },
    "efficiency": {
      "type": "number",
      "minimum": 0.5,
      "maximum": 1,
      "default": 0.9,
      "description": "Inverter efficiency (0.5-1.0). Good pure-sine inverters are 0.90-0.95. Modified-sine are 0.85-0.90. Budget units may be lower."
    },
    "derating_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 50,
      "default": 20,
      "description": "Derating percentage for temperature, altitude, and safety margin. NEC recommends 20% (80% continuous rating). Range 0-50%."
    }
  },
  "required": [
    "continuous_watts"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

pcb_layout

Turn a SPICE netlist into a fab-ready 2-layer PCB: assigns real footprints (0805, TO-92, DO-35, DIP-8, headers, LED, radial-cap), auto-places components (connectivity-aware; or use your own placement), routes a 2-layer maze router with vias, and VERIFIES the result with DRC (clearance/crossing checks) and ERC (union-find copper connectivity proven against the netlist). Returns the board, routing stats + honest unrouted-net list, DRC violations, ERC net status, a 'manufacturable' flag (true only when DRC+ERC clean and everything routed), SVG layers (top/bottom copper, silkscreen, drill, assembly), and optional Gerber RS-274X + Excellon drill files. Same netlist you simulate with spice_simulate — design, verify, and lay out an entire board through the tool layer. Supply a 'placement' array for production-quality boards; the auto-router is a first-pass best-of-N-seeds.

Parameters7

netlist	string	required	SPICE netlist (same format as spice_simulate). Components + nets are extracted; .model/.tran/etc. ignored.
placement	array	optional	Optional manual placement; omit for connectivity-aware auto-placement (best of N seeds).
board	object	optional	Optional board size in mm; auto-sized if omitted
clearance_mm	number	optional	Minimum copper clearance in mm
trace_width_mm	number	optional	Routing trace width in mm
gnd_pour	boolean	optional	Treat GND as a bottom-layer pour (unions all GND pads for ERC)
gerber	boolean	optional	Also return Gerber RS-274X + Excellon drill files

Raw schema

{
  "type": "object",
  "properties": {
    "netlist": {
      "type": "string",
      "minLength": 5,
      "description": "SPICE netlist (same format as spice_simulate). Components + nets are extracted; .model/.tran/etc. ignored."
    },
    "placement": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "ref": {
            "type": "string",
            "description": "Component reference (e.g. 'Q1')"
          },
          "x": {
            "type": "number",
            "description": "X position of component center in mm"
          },
          "y": {
            "type": "number",
            "description": "Y position in mm"
          },
          "rot": {
            "type": "number",
            "description": "Rotation in degrees (0/90/180/270)"
          }
        },
        "required": [
          "ref",
          "x",
          "y"
        ],
        "additionalProperties": false
      },
      "description": "Optional manual placement; omit for connectivity-aware auto-placement (best of N seeds)."
    },
    "board": {
      "type": "object",
      "properties": {
        "w": {
          "type": "number"
        },
        "h": {
          "type": "number"
        }
      },
      "required": [
        "w",
        "h"
      ],
      "additionalProperties": false,
      "description": "Optional board size in mm; auto-sized if omitted"
    },
    "clearance_mm": {
      "type": "number",
      "default": 0.2,
      "description": "Minimum copper clearance in mm"
    },
    "trace_width_mm": {
      "type": "number",
      "default": 0.25,
      "description": "Routing trace width in mm"
    },
    "gnd_pour": {
      "type": "boolean",
      "default": false,
      "description": "Treat GND as a bottom-layer pour (unions all GND pads for ERC)"
    },
    "gerber": {
      "type": "boolean",
      "default": false,
      "description": "Also return Gerber RS-274X + Excellon drill files"
    }
  },
  "required": [
    "netlist"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

voltage_divider

Calculates output voltage, current draw, and power dissipation for a resistive voltage divider. Given an input voltage Vin and two resistor values R1 (upper) and R2 (lower), computes Vout = Vin * R2 / (R1 + R2), divider current, individual resistor power dissipation, and the division ratio. Essential for biasing circuits, level shifting, ADC input scaling, and feedback networks. Use before trace_width to size traces for divider current, or chain from a power supply output to verify signal levels.

Parameters3

vin	number	required	Input voltage in volts (V). Must be positive.
r1_ohm	number	required	Upper resistor value in ohms (R1), connected between Vin and Vout node.
r2_ohm	number	required	Lower resistor value in ohms (R2), connected between Vout node and ground.

Raw schema

{
  "type": "object",
  "properties": {
    "vin": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Input voltage in volts (V). Must be positive."
    },
    "r1_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Upper resistor value in ohms (R1), connected between Vin and Vout node."
    },
    "r2_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Lower resistor value in ohms (R2), connected between Vout node and ground."
    }
  },
  "required": [
    "vin",
    "r1_ohm",
    "r2_ohm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

rc_filter

Computes the cutoff frequency, time constant, impedance, and phase shift of a first-order RC filter. Supports both lowpass and highpass topologies. The cutoff frequency is f = 1/(2*pi*R*C) where the signal is attenuated by 3 dB. The time constant tau = R*C governs transient response — the capacitor reaches 63.2% of its final value after one tau. Use for anti-aliasing before ADCs, DC blocking, noise filtering, and signal conditioning. Chain from voltage_divider to design filtered bias networks.

Parameters3

resistance_ohm	number	required	Resistance in ohms (R). The resistive element of the RC filter.
capacitance_f	number	required	Capacitance in farads (C). The capacitive element of the RC filter.
filter_type	string	optional	Filter topology: 'lowpass' (R then C to ground) or 'highpass' (C then R to ground).

Raw schema

{
  "type": "object",
  "properties": {
    "resistance_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Resistance in ohms (R). The resistive element of the RC filter."
    },
    "capacitance_f": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Capacitance in farads (C). The capacitive element of the RC filter."
    },
    "filter_type": {
      "type": "string",
      "enum": [
        "lowpass",
        "highpass"
      ],
      "default": "lowpass",
      "description": "Filter topology: 'lowpass' (R then C to ground) or 'highpass' (C then R to ground)."
    }
  },
  "required": [
    "resistance_ohm",
    "capacitance_f"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

lc_resonance

Calculates the resonant frequency of an LC circuit, along with optional Q factor and bandwidth when series resistance is provided. The resonant frequency f0 = 1/(2*pi*sqrt(L*C)) is where inductive and capacitive reactances cancel. Used for designing tank circuits, oscillators, bandpass filters, and antenna matching networks. If resistance R is given, computes quality factor Q = (1/R)*sqrt(L/C) and 3 dB bandwidth = f0/Q. Chain into impedance_match to design matching networks at the resonant frequency.

Parameters3

inductance_h	number	required	Inductance in henries (H). The inductive element of the LC circuit.
capacitance_f	number	required	Capacitance in farads (F). The capacitive element of the LC circuit.
resistance_ohm	number	optional	Optional series resistance in ohms for Q factor and bandwidth calculation. Omit for ideal LC analysis.

Raw schema

{
  "type": "object",
  "properties": {
    "inductance_h": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Inductance in henries (H). The inductive element of the LC circuit."
    },
    "capacitance_f": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Capacitance in farads (F). The capacitive element of the LC circuit."
    },
    "resistance_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Optional series resistance in ohms for Q factor and bandwidth calculation. Omit for ideal LC analysis."
    }
  },
  "required": [
    "inductance_h",
    "capacitance_f"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

impedance_match

Designs an L-network impedance matching circuit between two real impedances at a given frequency. Computes the required shunt and series reactive components (inductor and capacitor) to transform the source impedance to the load impedance. The network Q factor is sqrt(Rh/Rl - 1) where Rh is the higher impedance. Topology is automatically selected: the shunt element is placed across the higher impedance side. Essential for antenna matching, amplifier input/output matching, and maximizing power transfer. Chain from lc_resonance to match at a tank circuit's resonant frequency.

Parameters3

source_ohm	number	required	Source impedance in ohms (real, resistive). Must differ from load impedance.
load_ohm	number	required	Load impedance in ohms (real, resistive). Must differ from source impedance.
freq_mhz	number	required	Design frequency in megahertz for component value calculation.

Raw schema

{
  "type": "object",
  "properties": {
    "source_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Source impedance in ohms (real, resistive). Must differ from load impedance."
    },
    "load_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Load impedance in ohms (real, resistive). Must differ from source impedance."
    },
    "freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Design frequency in megahertz for component value calculation."
    }
  },
  "required": [
    "source_ohm",
    "load_ohm",
    "freq_mhz"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

trace_width

Calculates the minimum PCB trace width for a given current using the IPC-2221 standard formula. The IPC-2221 empirical equation relates current capacity to cross-sectional area and temperature rise: I = k * dT^0.44 * A^0.725, where k=0.048 for external layers and k=0.024 for internal layers. Supports configurable copper weight (oz/ft^2) and temperature rise. Also computes approximate DC resistance per centimeter. Essential for power delivery, high-current motor drivers, and ensuring PCB reliability. Chain from voltage_divider or impedance_match to verify trace sizing for computed currents.

Parameters4

current_amps	number	required	Required current capacity in amperes (A).
copper_oz	number	optional	Copper weight in ounces per square foot. 1 oz/ft^2 = 1.37 mil (34.8 um) thickness. Common values: 0.5, 1, 2.
temp_rise_c	number	optional	Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C.
layer	string	optional	PCB layer type. External layers dissipate heat better (k=0.048); internal layers use k=0.024.

Raw schema

{
  "type": "object",
  "properties": {
    "current_amps": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Required current capacity in amperes (A)."
    },
    "copper_oz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Copper weight in ounces per square foot. 1 oz/ft^2 = 1.37 mil (34.8 um) thickness. Common values: 0.5, 1, 2."
    },
    "temp_rise_c": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 10,
      "description": "Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C."
    },
    "layer": {
      "type": "string",
      "enum": [
        "external",
        "internal"
      ],
      "default": "external",
      "description": "PCB layer type. External layers dissipate heat better (k=0.048); internal layers use k=0.024."
    }
  },
  "required": [
    "current_amps"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

ohms_law

Solves Ohm's Law and the power equation given any two of four electrical quantities: voltage (V), current (I), resistance (R), and power (P). Uses V=IR, P=VI, P=I^2R, and P=V^2/R to derive the missing two values. Fundamental for every circuit design task: sizing resistors, estimating current draw, checking power dissipation, and verifying component ratings. Chain into led_resistor for LED circuits or voltage_divider for bias networks.

Parameters4

voltage_v	number	optional	Voltage in volts (V). Provide exactly 2 of the 4 parameters.
current_a	number	optional	Current in amps (A). Provide exactly 2 of the 4 parameters.
resistance_ohm	number	optional	Resistance in ohms. Provide exactly 2 of the 4 parameters.
power_w	number	optional	Power in watts (W). Provide exactly 2 of the 4 parameters.

Raw schema

{
  "type": "object",
  "properties": {
    "voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Voltage in volts (V). Provide exactly 2 of the 4 parameters."
    },
    "current_a": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Current in amps (A). Provide exactly 2 of the 4 parameters."
    },
    "resistance_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Resistance in ohms. Provide exactly 2 of the 4 parameters."
    },
    "power_w": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Power in watts (W). Provide exactly 2 of the 4 parameters."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

resistor_color_code

Decodes 4-band or 5-band resistor color codes into resistance value, tolerance, and min/max range. Accepts an ordered array of color names (left-to-right as printed on the resistor body). Supports standard EIA color codes including gold and silver multiplier/tolerance bands. Outputs the nominal resistance in ohms, a human-readable formatted value (e.g. '4.7kΩ'), tolerance percentage, and the min/max resistance range. Chain into ohms_law or led_resistor for circuit analysis.

Parameters1

bands

array

required

Array of 4 or 5 color band names from left to right. 4-band: [digit1, digit2, multiplier, tolerance]. 5-band: [digit1, digit2, digit3, multiplier, tolerance].

Raw schema

{
  "type": "object",
  "properties": {
    "bands": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "black",
          "brown",
          "red",
          "orange",
          "yellow",
          "green",
          "blue",
          "violet",
          "grey",
          "white",
          "gold",
          "silver",
          "none"
        ]
      },
      "description": "Array of 4 or 5 color band names from left to right. 4-band: [digit1, digit2, multiplier, tolerance]. 5-band: [digit1, digit2, digit3, multiplier, tolerance]."
    }
  },
  "required": [
    "bands"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

led_resistor

Calculates the current-limiting resistor for driving one or more LEDs in series from a DC supply. Computes the exact resistance from R = (Vsupply - n*Vf) / I, then selects the nearest E24 standard resistor value. Reports the actual current with the standard resistor, power dissipation, and voltage across the resistor. Supports series LED strings by specifying led_count. Validates that supply voltage exceeds total forward voltage. Chain from ohms_law for power budgeting or into trace_width for PCB layout.

Parameters4

supply_voltage_v	number	required	Supply voltage in volts (V). Must be positive.
led_forward_v	number	optional	LED forward voltage in volts (V). Defaults to 2.0V (typical red LED).
led_current_ma	number	optional	Desired LED current in milliamps (mA). Defaults to 20mA.
led_count	integer	optional	Number of LEDs in series. Defaults to 1.

Raw schema

{
  "type": "object",
  "properties": {
    "supply_voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Supply voltage in volts (V). Must be positive."
    },
    "led_forward_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 2,
      "description": "LED forward voltage in volts (V). Defaults to 2.0V (typical red LED)."
    },
    "led_current_ma": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 20,
      "description": "Desired LED current in milliamps (mA). Defaults to 20mA."
    },
    "led_count": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Number of LEDs in series. Defaults to 1."
    }
  },
  "required": [
    "supply_voltage_v"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

timer_555

Calculates timing parameters for the ubiquitous NE555 / LM555 timer IC in astable (free-running oscillator) and monostable (one-shot pulse) modes. In astable mode, computes frequency, period, duty cycle, and HIGH/LOW durations from R1, R2, and C using f = 1.44 / ((R1 + 2·R2) · C). In monostable mode, computes pulse width from R and C using t = 1.1 · R · C. Standard 555 astable duty cycle is always >50%; for 50% duty cycle use a diode across R2. Useful for generating clock signals, PWM, delays, and debounce circuits. Chain from ohms_law for power calculations or resistor_color_code for component selection.

Parameters4

mode	string	required	Operating mode. 'astable' produces a continuous square wave. 'monostable' produces a single timed pulse.
r1_ohm	number	required	Resistance R1 in ohms. In astable mode this is the charge-path resistor between Vcc and the discharge pin. In monostable mode this is the timing resistor.
r2_ohm	number	optional	Resistance R2 in ohms (astable mode only). Charge/discharge resistor between the discharge and threshold pins. Required for astable mode.
c_farad	number	required	Timing capacitor in farads. Typical values range from 1 pF to 1000 µF. Use scientific notation, e.g. 1e-6 for 1 µF.

Raw schema

{
  "type": "object",
  "properties": {
    "mode": {
      "type": "string",
      "enum": [
        "astable",
        "monostable"
      ],
      "description": "Operating mode. 'astable' produces a continuous square wave. 'monostable' produces a single timed pulse."
    },
    "r1_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Resistance R1 in ohms. In astable mode this is the charge-path resistor between Vcc and the discharge pin. In monostable mode this is the timing resistor."
    },
    "r2_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Resistance R2 in ohms (astable mode only). Charge/discharge resistor between the discharge and threshold pins. Required for astable mode."
    },
    "c_farad": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Timing capacitor in farads. Typical values range from 1 pF to 1000 µF. Use scientific notation, e.g. 1e-6 for 1 µF."
    }
  },
  "required": [
    "mode",
    "r1_ohm",
    "c_farad"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

op_amp_gain

Calculate voltage gain and output for operational amplifier circuits in inverting, non-inverting, and differential configurations. For inverting: Av = -Rf/Ri with input impedance equal to Ri. For non-inverting: Av = 1 + Rf/Rg with very high input impedance. For differential: Av = Rf/Ri applied to (V1 - V2). Reports gain in linear and dB, output voltage when input is provided, input impedance, and phase inversion status. Ideal op-amp assumptions (infinite open-loop gain, zero input bias current). Chain from ohms_law for power budgeting or resistor_color_code for component selection.

Parameters5

topology	string	required	Op-amp circuit topology. 'inverting' uses Rf/Ri feedback with input to inverting terminal. 'non_inverting' applies input to non-inverting terminal with Rf/Rg feedback. 'differential' amplifies the voltage difference between two inputs.
rf_ohm	number	required	Feedback resistor Rf in ohms. Sets gain magnitude in all topologies.
ri_ohm	number	required	Input/gain resistor in ohms. For inverting: input resistor Ri. For non-inverting: ground resistor Rg. For differential: input resistor on both channels.
vin_v	number	optional	Input voltage in volts (optional). When provided, computes actual output voltage. For differential topology, this is V1 (non-inverting input).
vin2_v	number	optional	Second input voltage in volts (differential topology only). This is V2 (inverting input).

Raw schema

{
  "type": "object",
  "properties": {
    "topology": {
      "type": "string",
      "enum": [
        "inverting",
        "non_inverting",
        "differential"
      ],
      "description": "Op-amp circuit topology. 'inverting' uses Rf/Ri feedback with input to inverting terminal. 'non_inverting' applies input to non-inverting terminal with Rf/Rg feedback. 'differential' amplifies the voltage difference between two inputs."
    },
    "rf_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Feedback resistor Rf in ohms. Sets gain magnitude in all topologies."
    },
    "ri_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Input/gain resistor in ohms. For inverting: input resistor Ri. For non-inverting: ground resistor Rg. For differential: input resistor on both channels."
    },
    "vin_v": {
      "type": "number",
      "description": "Input voltage in volts (optional). When provided, computes actual output voltage. For differential topology, this is V1 (non-inverting input)."
    },
    "vin2_v": {
      "type": "number",
      "description": "Second input voltage in volts (differential topology only). This is V2 (inverting input)."
    }
  },
  "required": [
    "topology",
    "rf_ohm",
    "ri_ohm"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

capacitor_charge

Calculates RC capacitor charge timing, energy storage, and transient voltages. Given resistance, capacitance, supply voltage, and optional initial voltage, computes the RC time constant (τ = R×C), time to reach standard charge thresholds (63%, 86%, 95%, 99%), voltage at key time points, energy stored (E = ½CV²), and peak charging current. Optionally calculates time to reach a specific target voltage using t = -τ × ln((Vsupply - Vtarget) / (Vsupply - Vinitial)). Essential for timing circuits, power-on reset delays, debounce networks, and soft-start designs. Chain from rc_filter for frequency-domain analysis or timer_555 for oscillator timing.

Parameters5

resistance_ohm	number	required	Series resistance in ohms (R). Controls charge/discharge rate.
capacitance_f	number	required	Capacitance in farads (C). Use scientific notation, e.g. 1e-6 for 1 µF.
v_supply	number	required	Supply voltage in volts. The voltage the capacitor charges toward.
v_initial	number	optional	Initial capacitor voltage in volts (default 0 for fully discharged).
v_target	number	optional	Target voltage to reach in volts (optional). When provided, calculates time to reach this voltage. Must be between v_initial and v_supply.

Raw schema

{
  "type": "object",
  "properties": {
    "resistance_ohm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Series resistance in ohms (R). Controls charge/discharge rate."
    },
    "capacitance_f": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Capacitance in farads (C). Use scientific notation, e.g. 1e-6 for 1 µF."
    },
    "v_supply": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Supply voltage in volts. The voltage the capacitor charges toward."
    },
    "v_initial": {
      "type": "number",
      "default": 0,
      "description": "Initial capacitor voltage in volts (default 0 for fully discharged)."
    },
    "v_target": {
      "type": "number",
      "description": "Target voltage to reach in volts (optional). When provided, calculates time to reach this voltage. Must be between v_initial and v_supply."
    }
  },
  "required": [
    "resistance_ohm",
    "capacitance_f",
    "v_supply"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

pcb_via_current

Calculate PCB via current-carrying capacity using the IPC-2221 standard. A plated via is a hollow copper cylinder whose cross-sectional area is the annular ring of plating: A = pi * (D - t) * t, where D is the drill diameter and t is plating thickness. The IPC-2221 empirical formula I = k * dT^0.44 * A^0.725 (k=0.048) then gives the maximum current for a given temperature rise. Also computes via barrel resistance from copper resistivity (1.724e-6 ohm-cm) and barrel length (board thickness). When a target current is specified, returns how many parallel vias are needed. Essential for power planes, high-current paths, and thermal via arrays. Chain with trace_width to verify both trace and via can handle the same current.

Parameters5

drill_diameter_mm	number	optional	Via drill hole diameter in millimeters. Common values: 0.2 (microvia), 0.3 (standard), 0.4, 0.6, 0.8, 1.0.
plating_thickness_um	number	optional	Copper plating thickness on the via barrel wall in micrometers. Standard is 25 um (IPC Class 2). Heavy plating is 50 um (IPC Class 3).
board_thickness_mm	number	optional	Total PCB board thickness in millimeters. Standard 2-layer is 1.6 mm. Common values: 0.8, 1.0, 1.6, 2.0, 2.4.
temp_rise_c	number	optional	Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C.
target_current_a	number	optional	Optional target current in amperes. When provided, calculates how many parallel vias are needed to carry this current safely.

Raw schema

{
  "type": "object",
  "properties": {
    "drill_diameter_mm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 0.3,
      "description": "Via drill hole diameter in millimeters. Common values: 0.2 (microvia), 0.3 (standard), 0.4, 0.6, 0.8, 1.0."
    },
    "plating_thickness_um": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 25,
      "description": "Copper plating thickness on the via barrel wall in micrometers. Standard is 25 um (IPC Class 2). Heavy plating is 50 um (IPC Class 3)."
    },
    "board_thickness_mm": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1.6,
      "description": "Total PCB board thickness in millimeters. Standard 2-layer is 1.6 mm. Common values: 0.8, 1.0, 1.6, 2.0, 2.4."
    },
    "temp_rise_c": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 10,
      "description": "Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C."
    },
    "target_current_a": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Optional target current in amperes. When provided, calculates how many parallel vias are needed to carry this current safely."
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

power_supply_decoupling

Select bypass and bulk decoupling capacitors for IC power supply pins. Computes the target PDN (Power Distribution Network) impedance from supply current, voltage, and allowable ripple using Z_target = V_ripple / I_total. Recommends a ceramic bypass capacitor (high-frequency decoupling, placed closest to IC pins) and a bulk capacitor (low-frequency decoupling, near the regulator). Calculates the ceramic cap's self-resonant frequency assuming typical lead inductance, and checks whether ESR-induced ripple stays within limits. Essential for digital, analog, and mixed-signal PCB design. Chain with lc_resonance to verify the decoupling capacitor's resonant behavior, or with trace_width to size the power trace.

Parameters6

supply_current_ma	number	required	IC supply current draw in milliamps (mA). Use the maximum or typical from the datasheet.
supply_voltage_v	number	required	Supply voltage in volts (V). Common values: 1.8, 2.5, 3.3, 5.0, 12.0.
switching_freq_mhz	number	optional	Primary switching or clock frequency of the IC in MHz. Determines the target impedance frequency range.
max_ripple_mv	number	optional	Maximum allowable supply ripple in millivolts (mV). Typical: 50 mV for digital, 10 mV for analog/RF.
num_ics	integer	optional	Number of identical ICs sharing this supply rail. Scales the total current demand.
esr_mohm	number	optional	Equivalent series resistance (ESR) of the ceramic bypass capacitor in milliohms. Typical MLCC: 5-20 mohm.

Raw schema

{
  "type": "object",
  "properties": {
    "supply_current_ma": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "IC supply current draw in milliamps (mA). Use the maximum or typical from the datasheet."
    },
    "supply_voltage_v": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Supply voltage in volts (V). Common values: 1.8, 2.5, 3.3, 5.0, 12.0."
    },
    "switching_freq_mhz": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Primary switching or clock frequency of the IC in MHz. Determines the target impedance frequency range."
    },
    "max_ripple_mv": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 50,
      "description": "Maximum allowable supply ripple in millivolts (mV). Typical: 50 mV for digital, 10 mV for analog/RF."
    },
    "num_ics": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Number of identical ICs sharing this supply rail. Scales the total current demand."
    },
    "esr_mohm": {
      "type": "number",
      "minimum": 0,
      "default": 10,
      "description": "Equivalent series resistance (ESR) of the ceramic bypass capacitor in milliohms. Typical MLCC: 5-20 mohm."
    }
  },
  "required": [
    "supply_current_ma",
    "supply_voltage_v"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

log_calc

Compute logarithms of a positive number in any base. Returns the custom-base logarithm, natural logarithm (ln), common logarithm (log10), and binary logarithm (log2). Useful for signal processing (decibel calculations), information theory (entropy in bits), pH chemistry, and general scientific computation. Uses the change-of-base formula log_b(x) = ln(x) / ln(b). Feeds into exponent_calc for inverse operations and scientific_notation for order-of-magnitude analysis.

Parameters2

value	number	required	The positive number to compute the logarithm of
base	number	optional	The logarithm base (default 10). Must be positive and not equal to 1

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "The positive number to compute the logarithm of"
    },
    "base": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 10,
      "description": "The logarithm base (default 10). Must be positive and not equal to 1"
    }
  },
  "required": [
    "value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

sig_figs

Count significant figures in a number and optionally round to N significant figures. Accepts the number as a string to preserve trailing zeros (e.g. '1.200' has 4 sig figs). Applies standard sig fig rules: leading zeros do not count, trailing zeros after a decimal point count, trailing zeros before a decimal point are treated as significant. Also returns the number in scientific notation. Essential for laboratory measurements, error analysis, and maintaining proper precision in chained calculations.

Parameters2

number_str	string	required	The number as a string to preserve trailing zeros (e.g. '1.200')
round_to_n	integer	optional	Optionally round the number to this many significant figures

Raw schema

{
  "type": "object",
  "properties": {
    "number_str": {
      "type": "string",
      "description": "The number as a string to preserve trailing zeros (e.g. '1.200')"
    },
    "round_to_n": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "Optionally round the number to this many significant figures"
    }
  },
  "required": [
    "number_str"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

scientific_notation

Convert any number to scientific notation and engineering notation. Returns the coefficient, exponent, a formatted string with Unicode superscripts (e.g. '3.14 × 10²'), and engineering notation where the exponent is a multiple of 3. Useful for expressing very large or very small values compactly, common in physics, electronics (picofarads, gigahertz), and astronomy. Accepts output from sig_figs and log_calc for precision-aware formatting.

Parameters1

value

number

required

The number to convert to scientific notation

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "number",
      "description": "The number to convert to scientific notation"
    }
  },
  "required": [
    "value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

percentage_calc

Calculate what percentage one number is of another. Given a value and a total, returns the percentage, decimal form, and simplified fraction. For example, 3 out of 4 yields 75%, 0.75, and '3/4'. Commonly used for test scores, survey results, financial ratios, completion rates, and unit conversions. Chain with percentage_increase to compare successive measurements or use with test_grade for academic scoring.

Parameters2

value	number	required	The part or numerator value
total	number	required	The whole or denominator value (must not be zero)

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "number",
      "description": "The part or numerator value"
    },
    "total": {
      "type": "number",
      "description": "The whole or denominator value (must not be zero)"
    }
  },
  "required": [
    "value",
    "total"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

percentage_increase

Calculate the percentage change between an old value and a new value. Determines whether the change is an increase or decrease, the absolute change, and the percentage change. Essential for financial analysis (stock price changes, revenue growth), scientific measurements (before/ after experiments), performance benchmarks, and population statistics. A positive percentage indicates growth; negative indicates decline. Division by zero (old_value = 0) is handled gracefully.

Parameters2

old_value	number	required	The original or starting value
new_value	number	required	The new or ending value

Raw schema

{
  "type": "object",
  "properties": {
    "old_value": {
      "type": "number",
      "description": "The original or starting value"
    },
    "new_value": {
      "type": "number",
      "description": "The new or ending value"
    }
  },
  "required": [
    "old_value",
    "new_value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

exponent_calc

Compute the result of raising a base to an exponent (base^exponent). Handles positive and negative exponents, fractional exponents, and zero. Returns the numeric result and a scientific notation string for very large or very small results. Useful for compound interest calculations, exponential growth/decay models, physics power laws, and combinatorics. The inverse of log_calc; chain with scientific_notation for formatted display of extreme values.

Parameters2

base	number	required	The base number
exponent	number	required	The exponent (power) to raise the base to

Raw schema

{
  "type": "object",
  "properties": {
    "base": {
      "type": "number",
      "description": "The base number"
    },
    "exponent": {
      "type": "number",
      "description": "The exponent (power) to raise the base to"
    }
  },
  "required": [
    "base",
    "exponent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

square_root

Compute the square root of a non-negative number. Returns the decimal result, whether the input is a perfect square, and a simplified radical form (e.g. '√12' simplifies to '2√3'). For integer inputs, factors are extracted from under the radical sign. Useful for geometry (diagonal/hypotenuse calculations), statistics (standard deviation from variance), signal processing (RMS values), and general algebra. Chain with pythagorean_theorem for triangle side calculations.

Parameters1

value

number

required

The non-negative number to compute the square root of

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "number",
      "minimum": 0,
      "description": "The non-negative number to compute the square root of"
    }
  },
  "required": [
    "value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

circumference

Calculate the circumference and area of a circle given either a radius or diameter. Provide one or both; if both are given, radius takes precedence. Returns circumference (C = 2πr), area (A = πr²), and both radius and diameter for completeness. Common in mechanical engineering (pulley systems, pipe sizing), electronics (antenna loop calculations, coil winding), civil engineering (manhole covers, circular foundations), and everyday measurement tasks.

Parameters2

radius	number	optional	The radius of the circle (takes precedence over diameter)
diameter	number	optional	The diameter of the circle

Raw schema

{
  "type": "object",
  "properties": {
    "radius": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "The radius of the circle (takes precedence over diameter)"
    },
    "diameter": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "The diameter of the circle"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

slope_calc

Calculate the slope, y-intercept, line equation, angle, and distance between two points in a 2D Cartesian plane. Given coordinates (x1, y1) and (x2, y2), computes slope (rise/run), y-intercept, the equation in slope-intercept form (y = mx + b), angle in degrees relative to the x-axis, and Euclidean distance. Handles vertical and horizontal lines as special cases. Useful for surveying, civil engineering grade calculations, linear regression visualization, and physics kinematics problems.

Parameters4

x1	number	required	X-coordinate of the first point
y1	number	required	Y-coordinate of the first point
x2	number	required	X-coordinate of the second point
y2	number	required	Y-coordinate of the second point

Raw schema

{
  "type": "object",
  "properties": {
    "x1": {
      "type": "number",
      "description": "X-coordinate of the first point"
    },
    "y1": {
      "type": "number",
      "description": "Y-coordinate of the first point"
    },
    "x2": {
      "type": "number",
      "description": "X-coordinate of the second point"
    },
    "y2": {
      "type": "number",
      "description": "Y-coordinate of the second point"
    }
  },
  "required": [
    "x1",
    "y1",
    "x2",
    "y2"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

pythagorean_theorem

Solve for any side of a right triangle using the Pythagorean theorem (a² + b² = c²). Provide any two of the three sides (a, b, c) and the missing side is computed. Also returns the triangle area (0.5 * a * b), perimeter, and confirms it is a right triangle. Side c is always the hypotenuse. Fundamental to surveying, construction (squaring corners), navigation (distance calculations), physics (vector decomposition), and 3D graphics. Chain with slope_calc for coordinate geometry or square_root for simplified radical answers.

Parameters3

a	number	optional	Length of side a (leg)
b	number	optional	Length of side b (leg)
c	number	optional	Length of side c (hypotenuse)

Raw schema

{
  "type": "object",
  "properties": {
    "a": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Length of side a (leg)"
    },
    "b": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Length of side b (leg)"
    },
    "c": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Length of side c (hypotenuse)"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

p_value

Calculate the p-value for a z-score or t-statistic. Supports one-tailed (left or right) and two-tailed hypothesis tests using either the standard normal distribution or the Student's t-distribution when degrees of freedom are specified. Returns significance flags at the 0.01, 0.05, and 0.10 alpha levels. Essential for interpreting results from t-tests, z-tests, ANOVA post-hoc comparisons, and regression coefficients. Uses the Abramowitz & Stegun normal CDF approximation and regularized incomplete beta function for the t-distribution.

Parameters3

test_statistic	number	required	The z-score or t-statistic from your hypothesis test. Positive values indicate the observed value is above the null hypothesis mean.
test_type	string	optional	Tail type: one_tail_left (p from left), one_tail_right (p from right), or two_tail (both tails combined).
degrees_of_freedom	integer	optional	Degrees of freedom for the t-distribution. Omit to use the standard normal (z) distribution.

Raw schema

{
  "type": "object",
  "properties": {
    "test_statistic": {
      "type": "number",
      "description": "The z-score or t-statistic from your hypothesis test. Positive values indicate the observed value is above the null hypothesis mean."
    },
    "test_type": {
      "type": "string",
      "enum": [
        "one_tail_left",
        "one_tail_right",
        "two_tail"
      ],
      "default": "two_tail",
      "description": "Tail type: one_tail_left (p from left), one_tail_right (p from right), or two_tail (both tails combined)."
    },
    "degrees_of_freedom": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "Degrees of freedom for the t-distribution. Omit to use the standard normal (z) distribution."
    }
  },
  "required": [
    "test_statistic"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

confidence_interval

Calculate the confidence interval for a sample mean. Given a sample mean, sample size, standard deviation, and confidence level, computes the margin of error, lower and upper bounds, critical z-score, and standard error. Supports finite population correction (FPC) when a population size is provided, which narrows the interval for samples that are a large fraction of the population. Uses the Abramowitz & Stegun rational approximation for the inverse normal CDF to derive the critical z-value. Common in survey analysis, A/B testing, and quality control.

Parameters5

sample_mean	number	required	The observed sample mean (x-bar) around which the confidence interval is centered.
sample_size	integer	required	The number of observations in the sample (n). Must be a positive integer.
standard_deviation	number	required	The standard deviation of the sample or population. Must be a positive number.
confidence_level	number	optional	Confidence level as a decimal between 0 and 1 (e.g. 0.95 for 95%). Default is 0.95.
population_size	integer	optional	Total population size for finite population correction (FPC). Omit for infinite population assumption.

Raw schema

{
  "type": "object",
  "properties": {
    "sample_mean": {
      "type": "number",
      "description": "The observed sample mean (x-bar) around which the confidence interval is centered."
    },
    "sample_size": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "The number of observations in the sample (n). Must be a positive integer."
    },
    "standard_deviation": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "The standard deviation of the sample or population. Must be a positive number."
    },
    "confidence_level": {
      "type": "number",
      "exclusiveMinimum": 0,
      "exclusiveMaximum": 1,
      "default": 0.95,
      "description": "Confidence level as a decimal between 0 and 1 (e.g. 0.95 for 95%). Default is 0.95."
    },
    "population_size": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "Total population size for finite population correction (FPC). Omit for infinite population assumption."
    }
  },
  "required": [
    "sample_mean",
    "sample_size",
    "standard_deviation"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

sales_tax

Calculates total cost including sales tax for a purchase. Given a unit price, tax rate percentage, and optional quantity, computes the subtotal (price times quantity), the tax amount rounded to two decimal places, and the final total. Useful for estimating purchase costs across US states and municipalities with different tax rates, comparing pre-tax and post-tax prices, and budgeting. Chain into salary_to_hourly to see how many work-hours a purchase represents.

Parameters3

price	number	required	Unit price of the item in dollars (or any currency). Must be positive.
tax_rate_pct	number	optional	Sales tax rate as a percentage (e.g. 8.875 for 8.875%). Defaults to 0 — enter your local rate.
quantity	integer	optional	Number of items to purchase. Defaults to 1.

Raw schema

{
  "type": "object",
  "properties": {
    "price": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Unit price of the item in dollars (or any currency). Must be positive."
    },
    "tax_rate_pct": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Sales tax rate as a percentage (e.g. 8.875 for 8.875%). Defaults to 0 — enter your local rate."
    },
    "quantity": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "default": 1,
      "description": "Number of items to purchase. Defaults to 1."
    }
  },
  "required": [
    "price"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

salary_to_hourly

Converts compensation between annual salary, monthly pay, weekly pay, and hourly wage. Accepts any of the four pay periods as input and derives all others. Uses configurable hours per week (default 40) and weeks per year (default 52). Daily rate assumes an 8-hour workday; monthly is annual divided by 12. Useful for comparing job offers quoted in different pay periods, freelance rate-setting, and budgeting. Chain from sales_tax to see how many hours a purchase costs.

Parameters4

amount	number	required	The salary or wage amount to convert.
from_type	string	optional	The pay period of the input amount. Defaults to 'annual'.
hours_per_week	number	optional	Hours worked per week. Defaults to 40 for a standard full-time schedule.
weeks_per_year	number	optional	Working weeks per year. Defaults to 52. Use 50 to account for 2 weeks unpaid vacation.

Raw schema

{
  "type": "object",
  "properties": {
    "amount": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "The salary or wage amount to convert."
    },
    "from_type": {
      "type": "string",
      "enum": [
        "annual",
        "monthly",
        "weekly",
        "hourly"
      ],
      "default": "annual",
      "description": "The pay period of the input amount. Defaults to 'annual'."
    },
    "hours_per_week": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 40,
      "description": "Hours worked per week. Defaults to 40 for a standard full-time schedule."
    },
    "weeks_per_year": {
      "type": "number",
      "exclusiveMinimum": 0,
      "default": 52,
      "description": "Working weeks per year. Defaults to 52. Use 50 to account for 2 weeks unpaid vacation."
    }
  },
  "required": [
    "amount"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

loan_amortization

Computes a full loan amortization schedule given principal, annual interest rate, and term in months. Returns the fixed monthly payment, total interest, total payments, and a month-by-month breakdown of principal vs interest. Supports optional extra monthly payments — shows months saved and interest saved. Works for mortgages (30yr/15yr), auto loans, personal loans, and student loans. All currency-agnostic. Use with /run?page=1&page_size=12 to paginate the schedule array for context-friendly agent consumption.

Parameters4

principal	number	required	Loan principal amount in dollars (or any currency unit).
annual_rate_pct	number	required	Annual interest rate as a percentage (e.g., 6.5 for 6.5%).
term_months	integer	required	Loan term in months. Max 600 (50 years). Common values: 360 (30yr), 180 (15yr), 60 (5yr auto).
extra_payment	number	optional	Optional fixed extra monthly payment toward principal. Defaults to 0.

Raw schema

{
  "type": "object",
  "properties": {
    "principal": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Loan principal amount in dollars (or any currency unit)."
    },
    "annual_rate_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "description": "Annual interest rate as a percentage (e.g., 6.5 for 6.5%)."
    },
    "term_months": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 600,
      "description": "Loan term in months. Max 600 (50 years). Common values: 360 (30yr), 180 (15yr), 60 (5yr auto)."
    },
    "extra_payment": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Optional fixed extra monthly payment toward principal. Defaults to 0."
    }
  },
  "required": [
    "principal",
    "annual_rate_pct",
    "term_months"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

compound_interest

Calculates compound interest growth over time using the formula A = P(1 + r/n)^(nt). Given a principal, annual rate, duration in years, and compounding frequency, returns the future value, total interest earned, effective annual rate (APY), and a year-by-year growth schedule. Supports optional recurring monthly contributions for savings projections. Works for savings accounts, CDs, investment returns, and retirement planning. Currency-agnostic.

Parameters5

principal	number	required	Initial investment or deposit amount (any currency unit).
annual_rate_pct	number	required	Annual interest rate as a percentage (e.g., 5.5 for 5.5%).
years	number	required	Investment duration in years. Max 100.
compounds_per_year	integer	optional	How often interest compounds per year. Allowed: 1 (annually), 2 (semi-annually), 4 (quarterly), 12 (monthly), 52 (weekly), 365 (daily). Defaults to 12.
monthly_contribution	number	optional	Optional recurring monthly contribution added at each month. Defaults to 0.

Raw schema

{
  "type": "object",
  "properties": {
    "principal": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Initial investment or deposit amount (any currency unit)."
    },
    "annual_rate_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "description": "Annual interest rate as a percentage (e.g., 5.5 for 5.5%)."
    },
    "years": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 100,
      "description": "Investment duration in years. Max 100."
    },
    "compounds_per_year": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 365,
      "default": 12,
      "description": "How often interest compounds per year. Allowed: 1 (annually), 2 (semi-annually), 4 (quarterly), 12 (monthly), 52 (weekly), 365 (daily). Defaults to 12."
    },
    "monthly_contribution": {
      "type": "number",
      "minimum": 0,
      "default": 0,
      "description": "Optional recurring monthly contribution added at each month. Defaults to 0."
    }
  },
  "required": [
    "principal",
    "annual_rate_pct",
    "years"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

test_grade

Calculates a test or exam grade from the number of correct answers and total questions. Returns the percentage score, letter grade, points missed, and GPA points. Supports US grading (A/B/C/D/F with 4.0 GPA scale), UK grading (First/2:1/2:2/Third/Fail), and percentage-only mode. US thresholds: A>=90, B>=80, C>=70, D>=60, F<60. UK thresholds: First>=70, 2:1>=60, 2:2>=50, Third>=40, Fail<40. Useful for students checking scores and teachers computing class statistics.

Parameters3

correct	integer	required	Number of questions answered correctly. Must be a non-negative integer.
total	integer	required	Total number of questions on the test. Must be a positive integer.
grading_scale	string	optional	Grading scale to use. 'us' for A-F letter grades, 'uk' for First/2:1/2:2/Third/Fail, 'percentage_only' for just the percentage.

Raw schema

{
  "type": "object",
  "properties": {
    "correct": {
      "type": "integer",
      "minimum": 0,
      "description": "Number of questions answered correctly. Must be a non-negative integer."
    },
    "total": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "description": "Total number of questions on the test. Must be a positive integer."
    },
    "grading_scale": {
      "type": "string",
      "enum": [
        "us",
        "uk",
        "percentage_only"
      ],
      "default": "us",
      "description": "Grading scale to use. 'us' for A-F letter grades, 'uk' for First/2:1/2:2/Third/Fail, 'percentage_only' for just the percentage."
    }
  },
  "required": [
    "correct",
    "total"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

square_footage

Calculates area and perimeter for common shapes — rectangle, circle, or triangle — in both imperial and metric units. Returns area in square feet, square meters, and acres, plus perimeter in feet and meters. For rectangles: area = length * width, perimeter = 2*(length + width). For circles: area = pi * r^2, perimeter = 2 * pi * r. For triangles: area = 0.5 * base * height, perimeter approximated as base + height + sqrt(base^2 + height^2). Useful for real estate, flooring, landscaping, and construction estimates.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

unit_convert

Convert between units across 10 categories: length (m, km, mi, ft, in, yd, nmi), mass (kg, lb, oz, g, ton), volume (l, gal, ml, cup, fl_oz), area (m2, ft2, acre, hectare), speed (mps, kph, mph, knot), pressure (pa, psi, bar, atm, mmhg), energy (j, kwh, btu, cal, wh), data (b, kb, mb, gb, tb), time (s, ms, min, hr, day, year), and temperature (c, f, k). Accepts any value with source and target unit abbreviations. Returns the converted result with the formula used.

Parameters3

value	number	required	The numeric value to convert.
from	string	required	Source unit abbreviation (e.g., 'km', 'lb', 'f', 'psi', 'kwh'). Case-insensitive.
to	string	required	Target unit abbreviation (e.g., 'mi', 'kg', 'c', 'bar', 'btu'). Case-insensitive.

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "number",
      "description": "The numeric value to convert."
    },
    "from": {
      "type": "string",
      "description": "Source unit abbreviation (e.g., 'km', 'lb', 'f', 'psi', 'kwh'). Case-insensitive."
    },
    "to": {
      "type": "string",
      "description": "Target unit abbreviation (e.g., 'mi', 'kg', 'c', 'bar', 'btu'). Case-insensitive."
    }
  },
  "required": [
    "value",
    "from",
    "to"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

hex_converter

Convert numbers between hexadecimal, binary, decimal, and octal bases. Accepts any base as input (prefix 0x for hex, 0b for binary, 0o for octal, or plain decimal) and returns all four representations simultaneously. Also reports bit width, byte count, ASCII character (if printable), and signed interpretations (8-bit, 16-bit, 32-bit two's complement). Essential for embedded programming, register debugging, network protocol analysis, and color code conversion. Example: 0xFF → decimal 255, binary 0b11111111, octal 0o377, 8 bits, 1 byte.

Parameters1

value

string

required

The number to convert. Prefix with 0x for hex (0xFF), 0b for binary (0b1010), 0o for octal (0o17). Plain numbers are treated as decimal. Supports negative values with leading minus.

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "string",
      "description": "The number to convert. Prefix with 0x for hex (0xFF), 0b for binary (0b1010), 0o for octal (0o17). Plain numbers are treated as decimal. Supports negative values with leading minus."
    }
  },
  "required": [
    "value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

timestamp_converter

Convert between Unix timestamps and human-readable date/time formats. Accepts Unix epoch (in seconds or milliseconds), ISO 8601 strings, or 'now' for the current time. Returns both Unix seconds and milliseconds, ISO 8601 UTC string, date and time components, day of the week, relative time description ('2 hours ago'), and past/future indicator. Auto-detects whether a numeric input is seconds or milliseconds based on magnitude. Essential for debugging logs, API timestamps, cron scheduling, and time zone conversions.

Parameters1

value

string

required

A timestamp to convert. Accepts Unix epoch (seconds or milliseconds), ISO 8601 string (e.g. '2024-01-15T10:30:00Z'), or 'now' for the current time.

Raw schema

{
  "type": "object",
  "properties": {
    "value": {
      "type": "string",
      "description": "A timestamp to convert. Accepts Unix epoch (seconds or milliseconds), ISO 8601 string (e.g. '2024-01-15T10:30:00Z'), or 'now' for the current time."
    }
  },
  "required": [
    "value"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

bmi_calculator

Calculate Body Mass Index (BMI) from weight and height using the WHO standard formula. Supports metric (kg/cm) and imperial (lbs/inches) units. Returns the BMI value, WHO classification (Underweight, Normal, Overweight, Obese Class I-III), and the healthy weight range for the given height. Formula: BMI = weight_kg / (height_m)^2. Useful for health screening, fitness planning, and clinical intake forms.

Parameters3

weight	number	required	Body weight. Units determined by the 'unit' parameter.
height	number	required	Height. Units determined by the 'unit' parameter.
unit	string	optional	Unit system. 'metric' = kg and cm. 'imperial' = lbs and inches. Defaults to 'metric'.

Raw schema

{
  "type": "object",
  "properties": {
    "weight": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Body weight. Units determined by the 'unit' parameter."
    },
    "height": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Height. Units determined by the 'unit' parameter."
    },
    "unit": {
      "type": "string",
      "enum": [
        "metric",
        "imperial"
      ],
      "default": "metric",
      "description": "Unit system. 'metric' = kg and cm. 'imperial' = lbs and inches. Defaults to 'metric'."
    }
  },
  "required": [
    "weight",
    "height"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

tip_calculator

Calculate tip and split a restaurant bill among multiple people. Given a bill amount, tip percentage, and number of diners, returns the tip amount, total with tip, per-person share, and effective tip percentage. Supports rounding up to the nearest whole number for convenience. Defaults to 18% tip for 1 person. Currency-agnostic — works with any monetary unit.

Parameters4

bill_amount	number	required	Total bill amount before tip (any currency).
tip_pct	number	optional	Tip percentage. Common values: 15 (standard), 18 (good), 20 (great), 25 (excellent). Defaults to 18%.
split	integer	optional	Number of people splitting the bill. Defaults to 1 (no split).
round_up	boolean	optional	Round the total up to the nearest whole number. Defaults to false.

Raw schema

{
  "type": "object",
  "properties": {
    "bill_amount": {
      "type": "number",
      "exclusiveMinimum": 0,
      "description": "Total bill amount before tip (any currency)."
    },
    "tip_pct": {
      "type": "number",
      "minimum": 0,
      "maximum": 100,
      "default": 18,
      "description": "Tip percentage. Common values: 15 (standard), 18 (good), 20 (great), 25 (excellent). Defaults to 18%."
    },
    "split": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 100,
      "default": 1,
      "description": "Number of people splitting the bill. Defaults to 1 (no split)."
    },
    "round_up": {
      "type": "boolean",
      "default": false,
      "description": "Round the total up to the nearest whole number. Defaults to false."
    }
  },
  "required": [
    "bill_amount"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

date_difference

Calculate the difference between two dates in days, weeks, months, years, and business days. Accepts dates in YYYY-MM-DD format. Returns the absolute difference (order doesn't matter) plus a flag indicating whether the end date is in the future relative to start. Business days count only Monday through Friday. Useful for project planning, deadline tracking, contract duration calculations, and age computations.

Parameters2

start_date	string	required	Start date in YYYY-MM-DD format (e.g., '2024-01-15').
end_date	string	required	End date in YYYY-MM-DD format (e.g., '2024-12-31').

Raw schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Start date in YYYY-MM-DD format (e.g., '2024-01-15')."
    },
    "end_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "End date in YYYY-MM-DD format (e.g., '2024-12-31')."
    }
  },
  "required": [
    "start_date",
    "end_date"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Install

Tools (89)

fspllink_budgetdipolemicrostripdbm_convertnoise_figure_cascadevswrattenuator_pi

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://calc.engineer/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "calc": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://calc.engineer/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.