accueil / serveurs / Géo & Temps / engineer.calc/calc
engineer.calc/calc
serveur MCP (Model Context Protocol) · calc-engineer 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que engineer.calc/calc est sûr ?
Au dernier audit MCP Hub, le serveur MCP « engineer.calc/calc » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 89 outils
- attenuator_pi≈ 362 tokens
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.
Paramètres, retour & exemple (2)
Paramètresz0_ohm· number · optionnel
Characteristic impedance in ohms (default 50)attenuation_db· number · requis
Desired attenuation in decibels (positive value)
Exemple d'appel{"name": "attenuator_pi", "arguments": {"attenuation_db": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"r1_ohm": 1, "r2_ohm": 1, "r3_ohm": 1, "topology": "texte"}} - attenuator_tee≈ 363 tokens
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.
Paramètres, retour & exemple (2)
Paramètresz0_ohm· number · optionnel
Characteristic impedance in ohms (default 50)attenuation_db· number · requis
Desired attenuation in decibels (positive value)
Exemple d'appel{"name": "attenuator_tee", "arguments": {"attenuation_db": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"r1_ohm": 1, "r2_ohm": 1, "r3_ohm": 1, "topology": "texte"}} - battery_autonomy≈ 634 tokens
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).
Paramètres, retour & exemple (6)
Paramètresdod· number · optionnel
Depth of discharge (0-1), default 0.8 for lithiumdaily_kwh· number · requis
Daily energy consumption in kilowatt-hours (kWh)battery_kwh· number · requis
Total installed battery capacity in kWhmin_soc_pct· number · optionnel
Minimum state of charge percentage, default 20%round_trip_efficiency· number · optionnel
Battery round-trip efficiency (0-1), default 0.90 for lithium, use 0.80 for lead-acidavg_solar_contribution_pct· number · optionnel
Average solar contribution during autonomy period (0-100%), default 0 for worst-case
Exemple d'appel{"name": "battery_autonomy", "arguments": {"daily_kwh": 1, "battery_kwh": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"usable_kwh": 1, "autonomy_days": 1, "autonomy_hours": 1, "daily_deficit_kwh": 1, "battery_cycles_per_year": 1}} - battery_charge_time≈ 563 tokens
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.
Paramètres, retour & exemple (5)
Paramètresvoltage_v· number · optionnel
Nominal battery voltage for energy calculation (V), default 3.7 for Li-ionefficiency· number · optionnel
Charger efficiency factor (0-1), default 0.85capacity_mah· number · requis
Total battery capacity in milliamp-hours (mAh)initial_soc_pct· number · optionnel
Initial state of charge as percentage (0-100), default 0 (empty)charge_current_ma· number · requis
Charge current in milliamps (mA)
Exemple d'appel{"name": "battery_charge_time", "arguments": {"capacity_mah": 1, "charge_current_ma": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"c_rate": 1, "charge_time_hours": 1, "energy_required_wh": 1, "charge_time_minutes": 1}} - battery_life≈ 487 tokens
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.
Paramètres, retour & exemple (4)
Paramètresvoltage· number · optionnel
Nominal battery voltage (V), default 3.7 for Li-ionefficiency· number · optionnel
Discharge efficiency factor (0-1), accounts for conversion losses and derating, default 0.85capacity_mah· number · requis
Battery capacity in milliamp-hours (mAh)current_draw_ma· number · requis
Average current draw in milliamps (mA)
Exemple d'appel{"name": "battery_life", "arguments": {"capacity_mah": 1, "current_draw_ma": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"energy_wh": 1, "runtime_days": 1, "runtime_hours": 1, "effective_capacity_mah": 1}} - bmi_calculator≈ 482 tokens
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.
Paramètres, retour & exemple (3)
Paramètresunit· string · optionnel · metric | imperial
Unit system. 'metric' = kg and cm. 'imperial' = lbs and inches. Defaults to 'metric'.height· number · requis
Height. Units determined by the 'unit' parameter.weight· number · requis
Body weight. Units determined by the 'unit' parameter.
Exemple d'appel{"name": "bmi_calculator", "arguments": {"height": 1, "weight": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"bmi": 1, "category": "texte", "weight_unit": "texte", "healthy_weight_range_low": 1, "healthy_weight_range_high": 1}} - capacitor_charge≈ 860 tokens
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.
Paramètres, retour & exemple (5)
Paramètresv_supply· number · requis
Supply voltage in volts. The voltage the capacitor charges toward.v_target· number · optionnel
Target voltage to reach in volts (optional). When provided, calculates time to reach this voltage. Must be between v_initial and v_supply.v_initial· number · optionnel
Initial capacitor voltage in volts (default 0 for fully discharged).capacitance_f· number · requis
Capacitance in farads (C). Use scientific notation, e.g. 1e-6 for 1 µF.resistance_ohm· number · requis
Series resistance in ohms (R). Controls charge/discharge rate.
Exemple d'appel{"name": "capacitor_charge", "arguments": {"v_supply": 1, "capacitance_f": 1, "resistance_ohm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"tau_s": 1, "tau_ms": 1, "energy_mj": 1, "v_at_1tau": 1, "v_at_2tau": 1, "v_at_5tau": 1, "energy_joules": 1, "peak_current_ma": 1, "time_to_63pct_ms": 1, "time_to_86pct_ms": 1, "time_to_95pct_ms": 1, "time_to_99pct_ms": 1}} - channel_utilization≈ 526 tokens
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.
Paramètres, retour & exemple (4)
Paramètresnodes· integer · requis
Number of active nodes in the mesh network.airtime_ms· number · requis
Time-on-air per packet in milliseconds. Obtain from lora_airtime tool.max_duty_cycle_pct· number · optionnel
Maximum acceptable channel utilization percentage. Default 10% is a common Meshtastic guideline.messages_per_hour_per_node· number · optionnel
Average messages transmitted per hour per node. Includes position beacons and user messages.
Exemple d'appel{"name": "channel_utilization", "arguments": {"nodes": 1, "airtime_ms": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"headroom_pct": 1, "utilization_pct": 1, "packets_per_hour": 1, "max_nodes_at_limit": 1}} - circumference≈ 349 tokens
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.
Paramètres, retour & exemple (2)
Paramètresradius· number · optionnel
The radius of the circle (takes precedence over diameter)diameter· number · optionnel
The diameter of the circle
Exemple d'appel{"name": "circumference", "arguments": {"radius": 1, "diameter": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"area": 1, "radius": 1, "diameter": 1, "circumference": 1}} - compound_interest≈ 734 tokens
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.
Paramètres, retour & exemple (5)
Paramètresyears· number · requis
Investment duration in years. Max 100.principal· number · requis
Initial investment or deposit amount (any currency unit).annual_rate_pct· number · requis
Annual interest rate as a percentage (e.g., 5.5 for 5.5%).compounds_per_year· integer · optionnel
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 · optionnel
Optional recurring monthly contribution added at each month. Defaults to 0.
Exemple d'appel{"name": "compound_interest", "arguments": {"years": 1, "principal": 1, "annual_rate_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"schedule": [], "future_value": 1, "total_interest": 1, "total_contributions": 1, "effective_annual_rate_pct": 1}} - confidence_interval≈ 644 tokens
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.
Paramètres, retour & exemple (5)
Paramètressample_mean· number · requis
The observed sample mean (x-bar) around which the confidence interval is centered.sample_size· integer · requis
The number of observations in the sample (n). Must be a positive integer.population_size· integer · optionnel
Total population size for finite population correction (FPC). Omit for infinite population assumption.confidence_level· number · optionnel
Confidence level as a decimal between 0 and 1 (e.g. 0.95 for 95%). Default is 0.95.standard_deviation· number · requis
The standard deviation of the sample or population. Must be a positive number.
Exemple d'appel{"name": "confidence_interval", "arguments": {"sample_mean": 1, "sample_size": 1, "standard_deviation": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"z_score": 1, "lower_bound": 1, "upper_bound": 1, "standard_error": 1, "margin_of_error": 1, "confidence_level": 1}} - cooling_btu≈ 787 tokens
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.
Paramètres, retour & exemple (8)
Paramètresinsulation· string · optionnel · poor | average | good | excellent
Wall/ceiling insulation quality: poor (uninsulated garage), average (standard drywall), good (insulated interior), excellent (server room with vapor barrier)total_watts· number · requis
Total power consumption in watts — all power becomes heatsun_exposure· string · optionnel · none | partial | full
Solar heat gain: none (interior/basement room), partial (one exterior wall with window), full (multiple sun-facing windows)room_width_ft· number · optionnel
Room width in feettarget_temp_f· number · optionnel
Desired room temperature in degrees Fahrenheitambient_temp_f· number · optionnel
Ambient temperature outside the room in degrees Fahrenheitroom_height_ft· number · optionnel
Room ceiling height in feetroom_length_ft· number · optionnel
Room length in feet
Exemple d'appel{"name": "cooling_btu", "arguments": {"total_watts": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ac_tons": 1, "total_btu": 1, "envelope_btu": 1, "equipment_btu": 1, "will_overheat": true, "exhaust_cfm_needed": 1, "mini_split_btu_recommended": 1}} - date_difference≈ 432 tokens
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.
Paramètres, retour & exemple (2)
Paramètresend_date· string · requis
End date in YYYY-MM-DD format (e.g., '2024-12-31').start_date· string · requis
Start date in YYYY-MM-DD format (e.g., '2024-01-15').
Exemple d'appel{"name": "date_difference", "arguments": {"end_date": "texte", "start_date": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"days": 1, "weeks": 1, "years": 1, "months": 1, "is_future": true, "business_days": 1}} - dbm_convert≈ 349 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdbm· number · requis
Power level in dBm (decibels relative to 1 milliwatt)impedance_ohm· number · optionnel
Load impedance in ohms for Vrms calculation (default 50)
Exemple d'appel{"name": "dbm_convert", "arguments": {"dbm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"mw": 1, "dbw": 1, "vrms": 1, "watts": 1}} - dipole≈ 370 tokens
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.
Paramètres, retour & exemple (2)
Paramètrestype· string · optionnel · half_wave | quarter_wave
Antenna type: half_wave dipole or quarter_wave monopolefreq_mhz· number · requis
Operating frequency in megahertz (MHz)
Exemple d'appel{"name": "dipole", "arguments": {"freq_mhz": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"length_m": 1, "length_ft": 1, "length_in": 1, "wavelength_m": 1}} - duty_cycle_budget≈ 565 tokens
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.
Paramètres, retour & exemple (2)
Paramètresregion· string · optionnel · EU868 | US915 | AS923 | AU915
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.airtime_ms· number · requis
Packet time-on-air in milliseconds. Obtain from the lora_airtime tool.
Exemple d'appel{"name": "duty_cycle_budget", "arguments": {"airtime_ms": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"duty_cycle_pct": 1, "min_interval_s": 1, "dwell_time_limited": true, "max_messages_per_hour": 1, "effective_data_rate_bps": 1}} - eirp_compliance≈ 682 tokens
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.
Paramètres, retour & exemple (5)
Paramètresregion· string · optionnel · FCC_US | ETSI_EU | ACMA_AU | IC_CA | JP | custom
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.tx_power_dbm· number · requis
Conducted transmit power at the radio output in dBm. Typical LoRa: 14-22 dBm.cable_loss_db· number · optionnel
Coaxial cable and connector loss in dB. Set 0 for devices with integrated antennas.antenna_gain_dbi· number · requis
Antenna gain in dBi. Stock Meshtastic antennas: 2-3 dBi. External: 6-10+ dBi.custom_limit_dbm· number · optionnel
Custom EIRP limit in dBm. Only used when region is 'custom'.
Exemple d'appel{"name": "eirp_compliance", "arguments": {"tx_power_dbm": 1, "antenna_gain_dbi": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"warning": "texte", "eirp_dbm": 1, "compliant": true, "limit_dbm": 1, "margin_db": 1, "eirp_watts": 1, "limit_watts": 1, "region_name": "texte"}} - exponent_calc≈ 308 tokens
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.
Paramètres, retour & exemple (2)
Paramètresbase· number · requis
The base numberexponent· number · requis
The exponent (power) to raise the base to
Exemple d'appel{"name": "exponent_calc", "arguments": {"base": 1, "exponent": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": 1, "scientific_notation": "texte"}} - fresnel_zone≈ 412 tokens
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.
Paramètres, retour & exemple (3)
Paramètresdist_km· number · requis
Total link distance in kilometresfreq_mhz· number · requis
Operating frequency in megahertz (MHz)zone_number· integer · optionnel
Fresnel zone number (1-5, default 1)
Exemple d'appel{"name": "fresnel_zone", "arguments": {"dist_km": 1, "freq_mhz": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"radius_m": 1, "radius_ft": 1, "wavelength_m": 1, "clearance_60pct_m": 1}} - fspl≈ 323 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdist_km· number · requis
Distance between transmitter and receiver in kilometresfreq_mhz· number · requis
Carrier frequency in megahertz (MHz)
Exemple d'appel{"name": "fspl", "arguments": {"dist_km": 1, "freq_mhz": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"fspl_db": 1, "wavelength_m": 1}} - generator_offset≈ 908 tokens
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.
Paramètres, retour & exemple (9)
Paramètresbattery_kwh· number · optionnel
Battery storage capacity in kWh (0 means no battery, generator needed at night), default 0daily_kwh_needed· number · requis
Total daily energy requirement in kWhyears_to_compare· integer · optionnel
Number of years to compare, default 10solar_system_cost_usd· number · requis
Total solar+battery system cost in USDgenerator_hours_per_day· number · optionnel
Generator runtime hours per day, default 8solar_daily_kwh_produced· number · requis
Daily solar energy production in kWhgenerator_consumption_gph· number · optionnel
Generator fuel consumption in gallons per hour at load, default 1.0generator_fuel_cost_per_gallon· number · optionnel
Fuel cost per gallon in USD, default $3.50generator_maintenance_per_1000hrs· number · optionnel
Generator maintenance cost per 1000 running hours in USD, default $200
Exemple d'appel{"name": "generator_offset", "arguments": {"daily_kwh_needed": 1, "solar_system_cost_usd": 1, "solar_daily_kwh_produced": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"savings_pct": 1, "savings_usd": 1, "breakeven_year": 1, "solar_coverage_pct": 1, "solar_total_cost_usd": 1, "solar_yearly_cost_usd": 1, "generator_total_cost_usd": 1, "generator_yearly_cost_usd": 1, "generator_hours_saved_per_year": 1}} - heatsink_cfd≈ 812 tokens
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.
Paramètres, retour & exemple (10)
Paramètresfin_count· integer · requis
Number of finsheat_load_w· number · requis
Total heat load applied to base in wattsbase_width_m· number · requis
Heatsink base width in metresfin_height_m· number · requis
Fin height in metresmesh_density· string · optionnel · coarse | medium | fine
Mesh densitybase_height_m· number · requis
Base plate thickness in metresbase_length_m· number · requis
Heatsink base length in metresambient_temp_c· number · optionnel
Ambient air temperature in Celsiusfin_thickness_m· number · requis
Fin thickness in metresairflow_velocity_ms· number · requis
Incoming airflow velocity in m/s
Exemple d'appel{"name": "heatsink_cfd", "arguments": {"fin_count": 1, "heat_load_w": 1, "base_width_m": 1, "fin_height_m": 1, "base_height_m": 1, "base_length_m": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"warnings": [], "mesh_cells": 1, "runtime_ms": 1, "fin_efficiency": 1, "fin_tip_temp_c": 1, "avg_base_temp_c": 1, "max_base_temp_c": 1, "pressure_drop_pa": 1, "optimal_fin_spacing_m": 1, "thermal_resistance_cw": 1}} - hex_converter≈ 608 tokens
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.
Paramètres, retour & exemple (1)
Paramètresvalue· string · requis
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.
Exemple d'appel{"name": "hex_converter", "arguments": {"value": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"hex": "texte", "bits": 1, "ascii": "texte", "bytes": 1, "octal": "texte", "binary": "texte", "decimal": 1, "signed_8": 1, "hex_upper": "texte", "signed_16": 1, "signed_32": 1}} - impedance_match≈ 716 tokens
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.
Paramètres, retour & exemple (3)
Paramètresfreq_mhz· number · requis
Design frequency in megahertz for component value calculation.load_ohm· number · requis
Load impedance in ohms (real, resistive). Must differ from source impedance.source_ohm· number · requis
Source impedance in ohms (real, resistive). Must differ from load impedance.
Exemple d'appel{"name": "impedance_match", "arguments": {"freq_mhz": 1, "load_ohm": 1, "source_ohm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"q_factor": 1, "topology": "texte", "shunt_component": {}, "series_component": {}}} - inverter_sizing≈ 1046 tokens
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.
Paramètres, retour & exemple (7)
Paramètresefficiency· number · optionnel
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.surge_watts· number · optionnel
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.derating_pct· number · optionnel
Derating percentage for temperature, altitude, and safety margin. NEC recommends 20% (80% continuous rating). Range 0-50%.power_factor· number · optionnel
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.system_voltage· string · optionnel · 12 | 24 | 48
DC system voltage. 12V for small/mobile, 24V for medium, 48V for large residential/commercial. Higher voltage = lower current = thinner cables.continuous_watts· number · requis
Total continuous load in watts. Sum of all appliances that may run simultaneously. Chain from solar_load_audit.peak_watts.largest_load_watts· number · optionnel
Wattage of the single largest appliance. Used to estimate surge if surge_watts is not provided. Chain from solar_load_audit.largest_load_watts.
Exemple d'appel{"name": "inverter_sizing", "arguments": {"continuous_watts": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"surge_margin_pct": 1, "required_surge_va": 1, "battery_cable_note": "texte", "dc_current_surge_a": 1, "derated_continuous_va": 1, "efficiency_loss_watts": 1, "recommended_size_watts": 1, "required_continuous_va": 1, "dc_current_continuous_a": 1}} - lc_resonance≈ 564 tokens
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.
Paramètres, retour & exemple (3)
Paramètresinductance_h· number · requis
Inductance in henries (H). The inductive element of the LC circuit.capacitance_f· number · requis
Capacitance in farads (F). The capacitive element of the LC circuit.resistance_ohm· number · optionnel
Optional series resistance in ohms for Q factor and bandwidth calculation. Omit for ideal LC analysis.
Exemple d'appel{"name": "lc_resonance", "arguments": {"inductance_h": 1, "capacitance_f": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"q_factor": 1, "bandwidth_hz": 1, "angular_freq_rad": 1, "resonant_freq_hz": 1, "resonant_freq_mhz": 1, "impedance_at_resonance_ohm": 1}} - led_resistor≈ 544 tokens
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.
Paramètres, retour & exemple (4)
Paramètresled_count· integer · optionnel
Number of LEDs in series. Defaults to 1.led_forward_v· number · optionnel
LED forward voltage in volts (V). Defaults to 2.0V (typical red LED).led_current_ma· number · optionnel
Desired LED current in milliamps (mA). Defaults to 20mA.supply_voltage_v· number · requis
Supply voltage in volts (V). Must be positive.
Exemple d'appel{"name": "led_resistor", "arguments": {"supply_voltage_v": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"resistance_ohm": 1, "nearest_e24_ohm": 1, "actual_current_ma": 1, "power_dissipation_mw": 1, "voltage_across_resistor_v": 1}} - link_budget≈ 508 tokens
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.
Paramètres, retour & exemple (6)
Paramètrestx_dbm· number · requis
Transmitter output power in dBmdist_km· number · requis
Link distance in kilometresfreq_mhz· number · requis
Carrier frequency in megahertz (MHz)rx_gain_dbi· number · optionnel
Receive antenna gain in dBi (default 2.15 for a half-wave dipole)tx_gain_dbi· number · optionnel
Transmit antenna gain in dBi (default 2.15 for a half-wave dipole)rx_sensitivity_dbm· number · optionnel
Receiver sensitivity in dBm; when provided, link margin is calculated
Exemple d'appel{"name": "link_budget", "arguments": {"tx_dbm": 1, "dist_km": 1, "freq_mhz": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"fspl_db": 1, "eirp_dbm": 1, "margin_db": 1, "rx_power_dbm": 1, "wavelength_m": 1}} - loan_amortization≈ 784 tokens
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.
Paramètres, retour & exemple (4)
Paramètresprincipal· number · requis
Loan principal amount in dollars (or any currency unit).term_months· integer · requis
Loan term in months. Max 600 (50 years). Common values: 360 (30yr), 180 (15yr), 60 (5yr auto).extra_payment· number · optionnel
Optional fixed extra monthly payment toward principal. Defaults to 0.annual_rate_pct· number · requis
Annual interest rate as a percentage (e.g., 6.5 for 6.5%).
Exemple d'appel{"name": "loan_amortization", "arguments": {"principal": 1, "term_months": 1, "annual_rate_pct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"schedule": [], "payoff_months": 1, "interest_saved": 1, "total_interest": 1, "total_payments": 1, "monthly_payment": 1, "total_extra_paid": 1}} - log_calc≈ 381 tokens
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.
Paramètres, retour & exemple (2)
Paramètresbase· number · optionnel
The logarithm base (default 10). Must be positive and not equal to 1value· number · requis
The positive number to compute the logarithm of
Exemple d'appel{"name": "log_calc", "arguments": {"value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"log2": 1, "log10": 1, "result": 1, "natural_log": 1}} - lora_airtime≈ 736 tokens
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.
Paramètres, retour & exemple (8)
Paramètrescr· integer · optionnel
LoRa coding rate denominator (5-8). Represents 4/5 through 4/8 FEC ratio.sf· integer · optionnel
LoRa spreading factor (7-12). Higher SF = longer range but slower data rate.crc· boolean · optionnel
Whether CRC is appended to payload. Recommended true for reliability.bw_khz· number · optionnel · 125 | 250 | 500
LoRa channel bandwidth in kHz. Common values: 125, 250, or 500.payload_bytes· integer · requis
Application payload size in bytes (0-255).explicit_header· boolean · optionnel
Whether to use explicit header mode. True for LoRaWAN; false for implicit header.preamble_symbols· integer · optionnel
Number of preamble symbols. LoRaWAN uses 8; raw LoRa may vary.low_data_rate_optimize· boolean · optionnel
Enable low data rate optimization. Auto-calculated if omitted: enabled for SF >= 11 at BW 125 kHz.
Exemple d'appel{"name": "lora_airtime", "arguments": {"payload_bytes": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"airtime_ms": 1, "data_rate_bps": 1, "symbol_time_ms": 1, "payload_symbols": 1, "preamble_time_ms": 1, "duty_cycle_1pct_interval_s": 1}} - lora_param_optimizer≈ 841 tokens
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.
Paramètres, retour & exemple (6)
Paramètresregion· string · optionnel · US915 | EU868 | AU915 | AS923
Regulatory region. Determines max TX power and duty cycle limit.terrain· string · optionnel · open | suburban | urban | dense_urban | indoor
Terrain type for path loss model. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.priority· string · optionnel · range | speed | battery | balanced
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.target_range_km· number · requis
Desired communication range in kilometers.antenna_gain_dbi· number · optionnel
Antenna gain in dBi. 2.15 = half-wave dipole reference.max_payload_bytes· integer · optionnel
Maximum payload size in bytes for airtime calculation.
Exemple d'appel{"name": "lora_param_optimizer", "arguments": {"target_range_km": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"airtime_ms": 1, "data_rate_bps": 1, "recommended_sf": 1, "estimated_range_km": 1, "recommended_bw_khz": 1, "recommended_tx_dbm": 1, "estimated_battery_hours": 1, "messages_per_hour_limit": 1}} - lora_range_estimate≈ 608 tokens
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.
Paramètres, retour & exemple (6)
Paramètrestx_dbm· number · optionnel
Transmit power in dBm. Typical LoRa: 14-30 dBm depending on region and module.terrain· string · optionnel · open | suburban | urban | dense_urban | indoor
Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.freq_mhz· number · optionnel
Carrier frequency in MHz. Common: 868 (EU), 915 (US/AU), 433 (Asia).rx_gain_dbi· number · optionnel
Receive antenna gain in dBi. 2.15 dBi = half-wave dipole.tx_gain_dbi· number · optionnel
Transmit antenna gain in dBi. 2.15 dBi = half-wave dipole.rx_sensitivity_dbm· number · optionnel
Receiver sensitivity in dBm. Typical LoRa SF10/BW125: -130 dBm. Varies by SF and bandwidth.
Exemple d'appel{"name": "lora_range_estimate", "arguments": {"tx_dbm": 1, "terrain": "open", "freq_mhz": 1, "rx_gain_dbi": 1, "tx_gain_dbi": 1, "rx_sensitivity_dbm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"max_range_km": 1, "margin_at_1km_db": 1, "effective_path_loss_db": 1}} - lora_sensitivity≈ 504 tokens
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.
Paramètres, retour & exemple (3)
Paramètressf· integer · optionnel
LoRa spreading factor (7-12). Higher SF = better sensitivity but slower data rate.bw_khz· number · optionnel · 125 | 250 | 500
LoRa channel bandwidth in kHz. Lower bandwidth = better sensitivity.noise_figure_db· number · optionnel
Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276).
Exemple d'appel{"name": "lora_sensitivity", "arguments": {"sf": 1, "bw_khz": 125, "noise_figure_db": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"noise_floor_dbm": 1, "required_snr_db": 1, "sensitivity_dbm": 1, "thermal_noise_dbm": 1}} - mah_to_wh≈ 383 tokens
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.
Paramètres, retour & exemple (2)
Paramètresvoltage_v· number · requis
Nominal battery voltage (V)capacity_mah· number · requis
Battery capacity in milliamp-hours (mAh)
Exemple d'appel{"name": "mah_to_wh", "arguments": {"voltage_v": 1, "capacity_mah": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"wh": 1, "kwh": 1, "mah": 1, "joules": 1, "voltage_v": 1}} - meshtastic_power≈ 860 tokens
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.
Paramètres, retour & exemple (8)
Paramètresrole· string · optionnel · client | router | repeater | client_muted
Meshtastic node role. client: sleeps between events. router: always listening. repeater: always listening, no display/BLE. client_muted: aggressive sleep.device· string · optionnel · heltec_v3 | rak_wisblock | tbeam | tbeam_supreme | station_g2 | custom
Meshtastic hardware device. Selects power consumption profile for sleep, RX, TX, GPS, and BLE.battery_mah· number · optionnel
Battery capacity in milliamp-hours. Common: 1100 (18650 min), 3000 (typical), 6000 (large).gps_enabled· boolean · optionnel
Whether GPS is enabled. Significantly increases power draw on devices with built-in GPS.channel_preset· string · optionnel · long_fast | long_moderate | long_slow | very_long_slow | medium_fast | medium_slow | short_fast | short_slow
Meshtastic channel preset. Affects TX airtime per message and thus power consumption.battery_voltage· number · optionnel
Nominal battery voltage. 3.7V for single-cell LiPo/Li-ion, 7.4V for 2S packs.bluetooth_enabled· boolean · optionnel
Whether Bluetooth is enabled for phone connection.messages_per_hour· number · optionnel
Expected messages sent and received per hour. Includes both TX and RX message events.
Exemple d'appel{"name": "meshtastic_power", "arguments": {"role": "client", "device": "heltec_v3", "battery_mah": 1, "gps_enabled": true, "channel_preset": "long_fast", "battery_voltage": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"daily_wh": 1, "rx_time_pct": 1, "tx_time_pct": 1, "runtime_days": 1, "runtime_hours": 1, "avg_current_ma": 1, "sleep_time_pct": 1}} - meshtastic_range≈ 940 tokens
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.
Paramètres, retour & exemple (8)
Paramètrescr· integer · optionnel
Custom coding rate denominator (5-8). Only used when channel_preset is 'custom'.sf· integer · optionnel
Custom spreading factor (7-12). Only used when channel_preset is 'custom'.bw_khz· number · optionnel
Custom bandwidth in kHz. Only used when channel_preset is 'custom'.device· string · optionnel · heltec_v3 | rak_wisblock | tbeam | tbeam_supreme | station_g2 | custom
Meshtastic hardware device. Selects default TX power, antenna gain, and noise figure. Use 'custom' to override all radio parameters manually.terrain· string · optionnel · open | suburban | urban | dense_urban | indoor
Terrain type for path loss correction. open: line-of-sight, suburban: light buildings, urban: moderate buildings, dense_urban: city center, indoor: inside buildings.tx_power_dbm· number · optionnel
Override device default transmit power in dBm.channel_preset· string · optionnel · long_fast | long_moderate | long_slow | very_long_slow | medium_fast | medium_slow | short_fast | short_slow
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.antenna_gain_dbi· number · optionnel
Override device default antenna gain in dBi. Useful for aftermarket antennas.
Exemple d'appel{"name": "meshtastic_range", "arguments": {"cr": 1, "sf": 1, "bw_khz": 1, "device": "heltec_v3", "terrain": "open", "tx_power_dbm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"device_name": "texte", "channel_name": "texte", "effective_sf": 1, "max_range_km": 1, "tx_power_dbm": 1, "link_budget_db": 1, "antenna_gain_dbi": 1, "effective_bw_khz": 1, "rx_sensitivity_dbm": 1}} - microstrip≈ 482 tokens
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.
Paramètres, retour & exemple (5)
Paramètreser· number · optionnel
Substrate relative dielectric constant (default 4.6 for FR-4)z0_ohm· number · optionnel
Target characteristic impedance in ohms (default 50)freq_mhz· number · optionnel
Optional frequency in MHz for effective wavelength calculationcopper_oz· number · optionnel
Copper weight in oz/ft2 (1 oz = 0.035 mm thickness)height_mm· number · requis
Substrate height (dielectric thickness) in millimetres
Exemple d'appel{"name": "microstrip", "arguments": {"height_mm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"er_eff": 1, "width_mm": 1, "wavelength_eff_mm": 1}} - network_bandwidth≈ 750 tokens
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.
Paramètres, retour & exemple (5)
Paramètreslink_speed_gbps· number · requis
Network link speed in gigabits per second (e.g. 1, 2.5, 5, 10, 25, 40, 100)concurrent_streams· integer · optionnel
Number of concurrent data streams / transfersprotocol_overhead_pct· number · optionnel
TCP/IP protocol overhead as a percentage (typically 3-5% for TCP, ~1% for UDP)stream_bandwidth_mbps· number · optionnel
Bandwidth required per stream in megabits per secondstorage_throughput_mbps· number · optionnel
Maximum storage read/write throughput in megabits per second. If provided, checks whether storage is the bottleneck
Exemple d'appel{"name": "network_bandwidth", "arguments": {"link_speed_gbps": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"saturated": true, "bottleneck": "texte", "headroom_mbps": 1, "utilization_pct": 1, "required_bandwidth_mbps": 1, "effective_bandwidth_mbps": 1, "time_to_transfer_1tb_hours": 1, "recommended_link_speed_gbps": 1}} - noise_figure_cascade≈ 383 tokens
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.
Paramètres, retour & exemple (1)
Paramètresstages· array · requis
Ordered array of receiver chain stages, each with nf_db and gain_db
Exemple d'appel{"name": "noise_figure_cascade", "arguments": {"stages": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total_nf_db": 1, "noise_temp_k": 1, "total_gain_db": 1}} - ohms_law≈ 417 tokens
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.
Paramètres, retour & exemple (4)
Paramètrespower_w· number · optionnel
Power in watts (W). Provide exactly 2 of the 4 parameters.current_a· number · optionnel
Current in amps (A). Provide exactly 2 of the 4 parameters.voltage_v· number · optionnel
Voltage in volts (V). Provide exactly 2 of the 4 parameters.resistance_ohm· number · optionnel
Resistance in ohms. Provide exactly 2 of the 4 parameters.
Exemple d'appel{"name": "ohms_law", "arguments": {"power_w": 1, "current_a": 1, "voltage_v": 1, "resistance_ohm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"power_w": 1, "current_a": 1, "voltage_v": 1, "resistance_ohm": 1}} - op_amp_gain≈ 762 tokens
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.
Paramètres, retour & exemple (5)
Paramètresvin_v· number · optionnel
Input voltage in volts (optional). When provided, computes actual output voltage. For differential topology, this is V1 (non-inverting input).rf_ohm· number · requis
Feedback resistor Rf in ohms. Sets gain magnitude in all topologies.ri_ohm· number · requis
Input/gain resistor in ohms. For inverting: input resistor Ri. For non-inverting: ground resistor Rg. For differential: input resistor on both channels.vin2_v· number · optionnel
Second input voltage in volts (differential topology only). This is V2 (inverting input).topology· string · requis · inverting | non_inverting | differential
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.
Exemple d'appel{"name": "op_amp_gain", "arguments": {"rf_ohm": 1, "ri_ohm": 1, "topology": "inverting"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"gain": 1, "rf_ohm": 1, "ri_ohm": 1, "vout_v": 1, "gain_db": 1, "gain_abs": 1, "topology": "texte", "phase_inversion": true, "input_impedance_ohm": 1}} - p_value≈ 586 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestest_type· string · optionnel · one_tail_left | one_tail_right | two_tail
Tail type: one_tail_left (p from left), one_tail_right (p from right), or two_tail (both tails combined).test_statistic· number · requis
The z-score or t-statistic from your hypothesis test. Positive values indicate the observed value is above the null hypothesis mean.degrees_of_freedom· integer · optionnel
Degrees of freedom for the t-distribution. Omit to use the standard normal (z) distribution.
Exemple d'appel{"name": "p_value", "arguments": {"test_statistic": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"p_value": 1, "test_type": "one_tail_left", "significant_at_01": true, "significant_at_05": true, "significant_at_10": true}} - pcb_layout≈ 719 tokens
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.
Paramètres, retour & exemple (7)
Paramètresboard· object · optionnel
Optional board size in mm; auto-sized if omittedgerber· boolean · optionnel
Also return Gerber RS-274X + Excellon drill filesnetlist· string · requis
SPICE netlist (same format as spice_simulate). Components + nets are extracted; .model/.tran/etc. ignored.gnd_pour· boolean · optionnel
Treat GND as a bottom-layer pour (unions all GND pads for ERC)placement· array · optionnel
Optional manual placement; omit for connectivity-aware auto-placement (best of N seeds).clearance_mm· number · optionnel
Minimum copper clearance in mmtrace_width_mm· number · optionnel
Routing trace width in mm
Exemple d'appel{"name": "pcb_layout", "arguments": {"netlist": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"drc": "texte", "erc": "texte", "nets": "texte", "board": "texte", "gerber": "texte", "routing": "texte", "warnings": [], "components": "texte", "layers_svg": "texte", "manufacturable": true}} - pcb_thermal≈ 944 tokens
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.
Paramètres, retour & exemple (7)
Paramètrescomponents· array · requis
Components on the boardmesh_density· string · optionnel · coarse | medium | fine
Mesh densityboard_width_m· number · requis
Board width in metresambient_temp_c· number · optionnel
Ambient temperature in Celsiusboard_length_m· number · requis
Board length in metresboard_thickness_m· number · optionnel
Board thickness in metres (default 1.6mm FR4)airflow_velocity_ms· number · optionnel
Airflow velocity in m/s (0 = natural convection)
Exemple d'appel{"name": "pcb_thermal", "arguments": {"components": [], "board_width_m": 1, "board_length_m": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"warnings": [], "mesh_cells": 1, "runtime_ms": 1, "violations": 1, "total_heat_w": 1, "component_temps": [], "avg_board_temp_c": 1, "max_board_temp_c": 1}} - pcb_via_current≈ 814 tokens
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.
Paramètres, retour & exemple (5)
Paramètrestemp_rise_c· number · optionnel
Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C.target_current_a· number · optionnel
Optional target current in amperes. When provided, calculates how many parallel vias are needed to carry this current safely.drill_diameter_mm· number · optionnel
Via drill hole diameter in millimeters. Common values: 0.2 (microvia), 0.3 (standard), 0.4, 0.6, 0.8, 1.0.board_thickness_mm· number · optionnel
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.plating_thickness_um· number · optionnel
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).
Exemple d'appel{"name": "pcb_via_current", "arguments": {"temp_rise_c": 1, "target_current_a": 1, "drill_diameter_mm": 1, "board_thickness_mm": 1, "plating_thickness_um": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"vias_needed": 1, "max_current_a": 1, "resistance_mohm": 1, "voltage_drop_mv": 1, "cross_section_mm2": 1, "cross_section_mil2": 1, "power_dissipation_mw": 1}} - percentage_calc≈ 324 tokens
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.
Paramètres, retour & exemple (2)
Paramètrestotal· number · requis
The whole or denominator value (must not be zero)value· number · requis
The part or numerator value
Exemple d'appel{"name": "percentage_calc", "arguments": {"total": 1, "value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"decimal": 1, "percentage": 1, "fraction_simplified": "texte"}} - percentage_increase≈ 372 tokens
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.
Paramètres, retour & exemple (2)
Paramètresnew_value· number · requis
The new or ending valueold_value· number · requis
The original or starting value
Exemple d'appel{"name": "percentage_increase", "arguments": {"new_value": 1, "old_value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"change": 1, "is_increase": true, "absolute_change": 1, "percentage_change": 1}} - power_cost≈ 786 tokens
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.
Paramètres, retour & exemple (4)
Paramètrespue· number · optionnel
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 spacesdevices· array · requis
List of devices with their wattagehours_per_day· number · optionnel
Hours per day the devices are runningkwh_rate_cents· number · optionnel
Electricity cost in cents per kilowatt-hour
Exemple d'appel{"name": "power_cost", "arguments": {"devices": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"daily_kwh": 1, "yearly_kwh": 1, "monthly_kwh": 1, "total_watts": 1, "amps_at_120v": 1, "amps_at_240v": 1, "breaker_15a_pct": 1, "yearly_cost_usd": 1, "monthly_cost_usd": 1, "total_with_pue_watts": 1}} - power_supply_decoupling≈ 945 tokens
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.
Paramètres, retour & exemple (6)
Paramètresnum_ics· integer · optionnel
Number of identical ICs sharing this supply rail. Scales the total current demand.esr_mohm· number · optionnel
Equivalent series resistance (ESR) of the ceramic bypass capacitor in milliohms. Typical MLCC: 5-20 mohm.max_ripple_mv· number · optionnel
Maximum allowable supply ripple in millivolts (mV). Typical: 50 mV for digital, 10 mV for analog/RF.supply_voltage_v· number · requis
Supply voltage in volts (V). Common values: 1.8, 2.5, 3.3, 5.0, 12.0.supply_current_ma· number · requis
IC supply current draw in milliamps (mA). Use the maximum or typical from the datasheet.switching_freq_mhz· number · optionnel
Primary switching or clock frequency of the IC in MHz. Determines the target impedance frequency range.
Exemple d'appel{"name": "power_supply_decoupling", "arguments": {"supply_voltage_v": 1, "supply_current_ma": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"bulk_cap_uf": 1, "bulk_cap_value": "texte", "ceramic_cap_uf": 1, "bypass_adequate": true, "ripple_at_esr_mv": 1, "total_current_ma": 1, "ceramic_cap_value": "texte", "target_impedance_ohm": 1, "self_resonant_freq_mhz": 1}} - pythagorean_theorem≈ 424 tokens
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.
Paramètres, retour & exemple (3)
Paramètresa· number · optionnel
Length of side a (leg)b· number · optionnel
Length of side b (leg)c· number · optionnel
Length of side c (hypotenuse)
Exemple d'appel{"name": "pythagorean_theorem", "arguments": {"a": 1, "b": 1, "c": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"a": 1, "b": 1, "c": 1, "area": 1, "perimeter": 1, "is_right_triangle": true}} - rack_capacity≈ 682 tokens
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.
Paramètres, retour & exemple (2)
Paramètresdevices· array · requis
List of devices to place in the rackrack_units· integer · optionnel
Total rack height in rack units (standard is 42U)
Exemple d'appel{"name": "rack_capacity", "arguments": {"devices": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"free_u": 1, "used_u": 1, "overhead_u": 1, "total_watts": 1, "total_weight_kg": 1, "utilization_pct": 1, "effective_free_u": 1, "total_weight_lbs": 1, "recommended_pdu_count": 1}} - raid_iops≈ 614 tokens
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.
Paramètres, retour & exemple (4)
Paramètresread_pct· number · optionnel
Percentage of workload that is reads (0-100). Typical: 70 for mixed, 90 for read-heavy, 30 for write-heavydisk_iops· number · optionnel
IOPS per individual disk. Typical values: HDD ~150, SATA SSD ~50000, NVMe SSD ~100000raid_type· string · optionnel · stripe | mirror | raidz1 | raidz2 | raidz3
RAID level: stripe (no redundancy, write penalty 1), mirror (write penalty 2), raidz1 (write penalty 2), raidz2 (write penalty 3), raidz3 (write penalty 4)disk_count· integer · requis
Total number of physical disks in the array
Exemple d'appel{"name": "raid_iops", "arguments": {"disk_count": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"read_iops": 1, "write_iops": 1, "blended_iops": 1, "write_penalty": 1, "estimated_latency_ms": 1}} - rc_filter≈ 551 tokens
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.
Paramètres, retour & exemple (3)
Paramètresfilter_type· string · optionnel · lowpass | highpass
Filter topology: 'lowpass' (R then C to ground) or 'highpass' (C then R to ground).capacitance_f· number · requis
Capacitance in farads (C). The capacitive element of the RC filter.resistance_ohm· number · requis
Resistance in ohms (R). The resistive element of the RC filter.
Exemple d'appel{"name": "rc_filter", "arguments": {"capacitance_f": 1, "resistance_ohm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"cutoff_freq_hz": 1, "cutoff_freq_khz": 1, "time_constant_s": 1, "time_constant_ms": 1, "phase_at_cutoff_deg": 1, "impedance_at_cutoff_ohm": 1}} - resistor_color_code≈ 461 tokens
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.
Paramètres, retour & exemple (1)
Paramètresbands· array · requis
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].
Exemple d'appel{"name": "resistor_color_code", "arguments": {"bands": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"max_ohm": 1, "min_ohm": 1, "band_count": 1, "tolerance_pct": 1, "resistance_ohm": 1, "resistance_formatted": "texte"}} - salary_to_hourly≈ 501 tokens
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.
Paramètres, retour & exemple (4)
Paramètresamount· number · requis
The salary or wage amount to convert.from_type· string · optionnel · annual | monthly | weekly | hourly
The pay period of the input amount. Defaults to 'annual'.hours_per_week· number · optionnel
Hours worked per week. Defaults to 40 for a standard full-time schedule.weeks_per_year· number · optionnel
Working weeks per year. Defaults to 52. Use 50 to account for 2 weeks unpaid vacation.
Exemple d'appel{"name": "salary_to_hourly", "arguments": {"amount": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"daily": 1, "annual": 1, "hourly": 1, "weekly": 1, "monthly": 1, "biweekly": 1}} - sales_tax≈ 428 tokens
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.
Paramètres, retour & exemple (3)
Paramètresprice· number · requis
Unit price of the item in dollars (or any currency). Must be positive.quantity· integer · optionnel
Number of items to purchase. Defaults to 1.tax_rate_pct· number · optionnel
Sales tax rate as a percentage (e.g. 8.875 for 8.875%). Defaults to 0 — enter your local rate.
Exemple d'appel{"name": "sales_tax", "arguments": {"price": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "subtotal": 1, "tax_amount": 1, "effective_rate_pct": 1}} - scientific_notation≈ 353 tokens
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.
Paramètres, retour & exemple (1)
Paramètresvalue· number · requis
The number to convert to scientific notation
Exemple d'appel{"name": "scientific_notation", "arguments": {"value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"exponent": 1, "coefficient": 1, "notation_string": "texte", "engineering_notation": "texte"}} - sig_figs≈ 382 tokens
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.
Paramètres, retour & exemple (2)
Paramètresnumber_str· string · requis
The number as a string to preserve trailing zeros (e.g. '1.200')round_to_n· integer · optionnel
Optionally round the number to this many significant figures
Exemple d'appel{"name": "sig_figs", "arguments": {"number_str": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"rounded_to_n": "texte", "sig_figs_count": 1, "scientific_notation": "texte"}} - slope_calc≈ 504 tokens
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.
Paramètres, retour & exemple (4)
Paramètresx1· number · requis
X-coordinate of the first pointx2· number · requis
X-coordinate of the second pointy1· number · requis
Y-coordinate of the first pointy2· number · requis
Y-coordinate of the second point
Exemple d'appel{"name": "slope_calc", "arguments": {"x1": 1, "x2": 1, "y1": 1, "y2": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"slope": 1, "distance": 1, "equation": "texte", "is_vertical": true, "y_intercept": 1, "angle_degrees": 1, "is_horizontal": true}} - snr_margin≈ 511 tokens
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.
Paramètres, retour & exemple (4)
Paramètressf· integer · optionnel
LoRa spreading factor (7-12). Higher SF tolerates lower SNR.bw_khz· number · optionnel · 125 | 250 | 500
LoRa channel bandwidth in kHz. Affects noise floor.rx_power_dbm· number · requis
Received signal power in dBm (e.g., -110). Typically from a link budget calculation or field measurement.noise_figure_db· number · optionnel
Receiver noise figure in dB. Typical LoRa radio NF is 6 dB (SX1276).
Exemple d'appel{"name": "snr_margin", "arguments": {"rx_power_dbm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"link_ok": true, "margin_db": 1, "noise_floor_dbm": 1, "required_snr_db": 1}} - solar_load_audit≈ 663 tokens
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.
Paramètres, retour & exemple (2)
Paramètresappliances· array · requis
List of appliances with wattage, hours per day, and quantitysafety_margin_pct· number · optionnel
Safety margin percentage to account for surge/inrush current, default 20%
Exemple d'appel{"name": "solar_load_audit", "arguments": {"appliances": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"peak_watts": 1, "total_daily_wh": 1, "appliance_count": 1, "total_daily_kwh": 1, "with_margin_kwh": 1, "largest_load_watts": 1, "recommended_inverter_va": 1}} - solar_roi≈ 857 tokens
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.
Paramètres, retour & exemple (10)
Paramètressystem_size_kw· number · requis
System size in kilowatts (kW)federal_itc_pct· number · optionnel
Federal Investment Tax Credit percentage, default 30% (US ITC)system_cost_usd· number · requis
Total installed system cost in USDstate_rebate_usd· number · optionnel
State or local rebate amount in USD, default 0annual_production_kwh· number · requis
Estimated annual energy production in kWh (from PVWatts or system_size_kw * peak_sun_hours * 365 * 0.80)system_lifetime_years· integer · optionnel
System lifetime in years, default 25annual_degradation_pct· number · optionnel
Annual panel degradation rate, default 0.5% per yearannual_maintenance_usd· number · optionnel
Annual maintenance cost in USD, default $100electricity_rate_cents· number · optionnel
Current electricity rate in cents per kWh, default 15annual_rate_increase_pct· number · optionnel
Annual utility rate increase percentage, default 3%
Exemple d'appel{"name": "solar_roi", "arguments": {"system_size_kw": 1, "system_cost_usd": 1, "annual_production_kwh": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"roi_pct": 1, "net_cost_usd": 1, "payback_years": 1, "total_savings_usd": 1, "lcoe_cents_per_kwh": 1, "year_1_savings_usd": 1, "year_25_savings_usd": 1, "lifetime_production_kwh": 1}} - solar_sizing≈ 687 tokens
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.
Paramètres, retour & exemple (7)
Paramètresdod· number · optionnel
Battery depth of discharge (0-1), default 0.8 for LiFePO4daily_kwh· number · requis
Daily energy consumption in kilowatt-hours (kWh)panel_watts· number · optionnel
Rated wattage per solar panel (W)peak_sun_hours· number · optionnel
Average peak sun hours per day for your location (hours)system_voltage· number · optionnel · 12 | 24 | 48
Battery bank system voltage: 12, 24, or 48 Vsystem_efficiency· number · optionnel
Overall system efficiency (0-1), accounts for inverter, wiring, and controller lossesbattery_autonomy_days· number · optionnel
Number of days the battery bank should sustain load without solar input
Exemple d'appel{"name": "solar_sizing", "arguments": {"daily_kwh": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"battery_ah": 1, "battery_kwh": 1, "panels_needed": 1, "daily_solar_kwh": 1, "total_panel_watts": 1, "charge_controller_amps": 1}} - spice_simulate≈ 939 tokens
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.
Paramètres, retour & exemple (7)
Paramètrescertify· boolean · optionnel
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.netlist· string · requis
SPICE netlist (ngspice-compatible). Must include at least one analysis command (.ac, .dc, .tran, .op) and end with .endoptions· object · optionnel
Additional ngspice .options (e.g. { reltol: 0.001 })analysis· string · optionnel · ac | dc | tran | op
Override analysis type (auto-detected from netlist if omitted)tolerances· object · optionnel
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 · optionnel
Node whose voltage is certified over the tolerance box (required with tolerances).temperature_c· number · optionnel
Simulation temperature in Celsius
Exemple d'appel{"name": "spice_simulate", "arguments": {"netlist": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"nodes": [], "fourier": "texte", "vectors": {}, "measures": "texte", "warnings": [], "runtime_ms": 1, "certificate": "texte", "analysis_type": "texte", "component_count": 1, "tolerance_certificate": "texte"}} - spice_template≈ 438 tokens
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.
Paramètres, retour & exemple (3)
Paramètresparams· object · requis
Template-specific parameters (e.g. r_ohms, c_farads, v_source)analysis· string · optionnel · ac | dc | tran
SPICE analysis type to include in netlisttemplate· string · requis · low_pass_rc | voltage_divider | common_emitter | rc_highpass | rlc_bandpass | opamp_inverting | diode_rectifier | wien_bridge
Circuit template name
Exemple d'appel{"name": "spice_template", "arguments": {"params": {}, "template": "low_pass_rc"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"netlist": "texte", "analysis_type": "texte", "template_name": "texte", "component_count": 1}} - square_footage≈ 314 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "square_footage", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"area_sqm": 1, "area_sqft": 1, "area_acres": 1, "perimeter_m": 1, "perimeter_ft": 1}} - square_root≈ 327 tokens
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.
Paramètres, retour & exemple (1)
Paramètresvalue· number · requis
The non-negative number to compute the square root of
Exemple d'appel{"name": "square_root", "arguments": {"value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": 1, "is_perfect_square": true, "simplified_radical": "texte"}} - string_sizing≈ 858 tokens
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.
Paramètres, retour & exemple (10)
Paramètresmppt_imax· number · requis
Maximum MPPT input current in ampsmppt_vmax· number · requis
Maximum MPPT input voltage in voltsmppt_vmin· number · requis
Minimum MPPT start/operating voltage in voltspanel_imp· number · requis
Panel maximum power current (Imp) at STC in ampspanel_isc· number · requis
Panel short circuit current (Isc) at STC in ampspanel_vmp· number · requis
Panel maximum power voltage (Vmp) at STC in voltspanel_voc· number · requis
Panel open circuit voltage (Voc) at STC in voltstemp_max_c· number · optionnel
Maximum expected cell temperature in Celsius, default 60temp_min_c· number · optionnel
Minimum expected site temperature in Celsius, default -10temp_coeff_voc_pct_per_c· number · optionnel
Voc temperature coefficient in %/C (negative for silicon), default -0.30
Exemple d'appel{"name": "string_sizing", "arguments": {"mppt_imax": 1, "mppt_vmax": 1, "mppt_vmin": 1, "panel_imp": 1, "panel_isc": 1, "panel_vmp": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"isc_total": 1, "array_watts": 1, "total_panels": 1, "vmp_hot_per_string": 1, "voc_cold_per_string": 1, "max_parallel_strings": 1, "max_panels_per_string": 1, "min_panels_per_string": 1, "recommended_panels_per_string": 1}} - subnet_calculator≈ 557 tokens
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.
Paramètres, retour & exemple (1)
Paramètrescidr· string · requis
IPv4 address in CIDR notation, e.g. 192.168.1.0/24
Exemple d'appel{"name": "subnet_calculator", "arguments": {"cidr": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ip_class": "texte", "last_usable": "texte", "subnet_mask": "texte", "total_hosts": 1, "first_usable": "texte", "usable_hosts": 1, "prefix_length": 1, "wildcard_mask": "texte", "network_address": "texte", "broadcast_address": "texte"}} - tcp_throughput≈ 576 tokens
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.
Paramètres, retour & exemple (4)
Paramètresrtt_ms· number · requis
Round-trip time (latency) in millisecondsmss_bytes· number · optionnel
Maximum Segment Size in bytes (typically 1460 for Ethernet)bandwidth_mbps· number · requis
Available link bandwidth in megabits per secondwindow_size_kb· number · optionnel
TCP receive window size in kilobytes
Exemple d'appel{"name": "tcp_throughput", "arguments": {"rtt_ms": 1, "bandwidth_mbps": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"bdp_kb": 1, "bdp_bytes": 1, "utilization_pct": 1, "window_sufficient": true, "max_throughput_mbps": 1, "recommended_window_kb": 1}} - test_grade≈ 483 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestotal· integer · requis
Total number of questions on the test. Must be a positive integer.correct· integer · requis
Number of questions answered correctly. Must be a non-negative integer.grading_scale· string · optionnel · us | uk | percentage_only
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.
Exemple d'appel{"name": "test_grade", "arguments": {"total": 1, "correct": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"gpa_points": 1, "percentage": 1, "letter_grade": "texte", "points_missed": 1}} - thermal_enclosure≈ 1120 tokens
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.
Paramètres, retour & exemple (10)
Paramètreswidth_m· number · requis
Enclosure width (Y) in metresheight_m· number · requis
Enclosure height (Z) in metreslength_m· number · requis
Enclosure length (X) in metresflow_type· string · requis · natural_convection | forced
Airflow typeheat_sources· array · requis
Heat sources inside the enclosuremesh_density· string · optionnel · coarse | medium | fine
Mesh density — coarse (~50K cells), medium (~200K), fine (~500K)ambient_temp_c· number · optionnel
Ambient air temperature in Celsiusinlet_position· string · optionnel · front_bottom | front_center | side_bottom
Inlet locationoutlet_position· string · optionnel · rear_top | rear_center | top_rear
Outlet locationinlet_velocity_ms· number · optionnel
Inlet air velocity in m/s (required for forced flow)
Exemple d'appel{"name": "thermal_enclosure", "arguments": {"width_m": 1, "height_m": 1, "length_m": 1, "flow_type": "natural_convection", "heat_sources": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"solver": "texte", "warnings": [], "avg_temp_c": 1, "iterations": 1, "max_temp_c": 1, "mesh_cells": 1, "min_temp_c": 1, "runtime_ms": 1, "total_heat_w": 1, "avg_velocity_ms": 1, "max_velocity_ms": 1, "hotspot_location": {}}} - timer_555≈ 773 tokens
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.
Paramètres, retour & exemple (4)
Paramètresmode· string · requis · astable | monostable
Operating mode. 'astable' produces a continuous square wave. 'monostable' produces a single timed pulse.r1_ohm· number · requis
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 · optionnel
Resistance R2 in ohms (astable mode only). Charge/discharge resistor between the discharge and threshold pins. Required for astable mode.c_farad· number · requis
Timing capacitor in farads. Typical values range from 1 pF to 1000 µF. Use scientific notation, e.g. 1e-6 for 1 µF.
Exemple d'appel{"name": "timer_555", "arguments": {"mode": "astable", "r1_ohm": 1, "c_farad": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"mode": "texte", "r1_ohm": 1, "r2_ohm": 1, "c_farad": 1, "period_s": 1, "c_display": "texte", "time_low_s": 1, "time_high_s": 1, "frequency_hz": 1, "duty_cycle_pct": 1}} - timestamp_converter≈ 502 tokens
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.
Paramètres, retour & exemple (1)
Paramètresvalue· string · requis
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.
Exemple d'appel{"name": "timestamp_converter", "arguments": {"value": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"is_past": true, "iso_8601": "texte", "iso_date": "texte", "iso_time": "texte", "relative": "texte", "day_of_week": "texte", "unix_seconds": 1, "unix_milliseconds": 1}} - tip_calculator≈ 481 tokens
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.
Paramètres, retour & exemple (4)
Paramètressplit· integer · optionnel
Number of people splitting the bill. Defaults to 1 (no split).tip_pct· number · optionnel
Tip percentage. Common values: 15 (standard), 18 (good), 20 (great), 25 (excellent). Defaults to 18%.round_up· boolean · optionnel
Round the total up to the nearest whole number. Defaults to false.bill_amount· number · requis
Total bill amount before tip (any currency).
Exemple d'appel{"name": "tip_calculator", "arguments": {"bill_amount": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "tip_amount": 1, "per_person_tip": 1, "per_person_total": 1, "effective_tip_pct": 1}} - trace_width≈ 548 tokens
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.
Paramètres, retour & exemple (4)
Paramètreslayer· string · optionnel · external | internal
PCB layer type. External layers dissipate heat better (k=0.048); internal layers use k=0.024.copper_oz· number · optionnel
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 · optionnel
Allowable temperature rise above ambient in degrees Celsius. IPC-2221 standard uses 10, 20, or 30 C.current_amps· number · requis
Required current capacity in amperes (A).
Exemple d'appel{"name": "trace_width", "arguments": {"current_amps": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"width_mm": 1, "area_mil2": 1, "width_mil": 1, "resistance_per_cm_mohm": 1}} - unit_convert≈ 432 tokens
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.
Paramètres, retour & exemple (3)
Paramètresto· string · requis
Target unit abbreviation (e.g., 'mi', 'kg', 'c', 'bar', 'btu'). Case-insensitive.from· string · requis
Source unit abbreviation (e.g., 'km', 'lb', 'f', 'psi', 'kwh'). Case-insensitive.value· number · requis
The numeric value to convert.
Exemple d'appel{"name": "unit_convert", "arguments": {"to": "texte", "from": "texte", "value": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": 1, "formula": "texte", "to_unit": "texte", "category": "texte", "from_unit": "texte"}} - ups_runtime≈ 632 tokens
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.
Paramètres, retour & exemple (7)
Paramètresva_rating· number · requis
UPS VA (volt-ampere) ratingbattery_ah· number · optionnel
Capacity per battery in amp-hours (Ah)efficiency· number · optionnel
Inverter/conversion efficiency (0-1), default 0.9load_watts· number · requis
Connected load in wattswatt_rating· number · requis
UPS real power (watt) ratingbattery_count· integer · optionnel
Number of batteries in the UPSbattery_voltage· number · optionnel
Voltage per battery (V)
Exemple d'appel{"name": "ups_runtime", "arguments": {"va_rating": 1, "load_watts": 1, "watt_rating": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"pf": 1, "load_pct": 1, "battery_wh": 1, "overloaded": true, "effective_wh": 1, "runtime_hours": 1, "runtime_minutes": 1}} - voltage_divider≈ 496 tokens
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.
Paramètres, retour & exemple (3)
Paramètresvin· number · requis
Input voltage in volts (V). Must be positive.r1_ohm· number · requis
Upper resistor value in ohms (R1), connected between Vin and Vout node.r2_ohm· number · requis
Lower resistor value in ohms (R2), connected between Vout node and ground.
Exemple d'appel{"name": "voltage_divider", "arguments": {"vin": 1, "r1_ohm": 1, "r2_ohm": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"vout": 1, "ratio": 1, "current_ma": 1, "power_r1_mw": 1, "power_r2_mw": 1, "total_power_mw": 1}} - voltage_drop≈ 584 tokens
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.
Paramètres, retour & exemple (5)
Paramètresconductor· string · optionnel · copper | aluminum
Conductor material: copper or aluminumvoltage_v· number · requis
System voltage (V)current_amps· number · requis
Load current in amperes (A)wire_length_m· number · requis
One-way wire length in meterswire_gauge_awg· number · requis
Wire gauge in AWG (e.g. 14, 12, 10; use negative for large gauges: -3 = 4/0)
Exemple d'appel{"name": "voltage_drop", "arguments": {"voltage_v": 1, "current_amps": 1, "wire_length_m": 1, "wire_gauge_awg": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"compliant": true, "power_loss_w": 1, "resistance_ohm": 1, "voltage_drop_v": 1, "voltage_drop_pct": 1, "voltage_at_load_v": 1}} - vswr≈ 467 tokens
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.
Paramètres, retour & exemple (3)
Paramètresvswr· number · optionnel
Voltage standing wave ratio (>= 1.0, where 1.0 is perfect match)return_loss_db· number · optionnel
Return loss in decibels (positive value, higher is better match)reflection_coefficient· number · optionnel
Reflection coefficient magnitude (gamma), 0 to 1
Exemple d'appel{"name": "vswr", "arguments": {"vswr": 1, "return_loss_db": 1, "reflection_coefficient": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"vswr": 1, "return_loss_db": 1, "mismatch_loss_db": 1, "power_reflected_pct": 1, "power_transmitted_pct": 1, "reflection_coefficient": 1}} - watts_to_amps≈ 404 tokens
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.
Paramètres, retour & exemple (2)
Paramètreswatts· number · requis
Power in watts (W)voltage_v· number · requis
Voltage in volts (V)
Exemple d'appel{"name": "watts_to_amps", "arguments": {"watts": 1, "voltage_v": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"amps": 1, "watts": 1, "milliamps": 1, "voltage_v": 1, "implied_resistance_ohm": 1}} - wavelength_freq≈ 384 tokens
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).
Paramètres, retour & exemple (2)
Paramètresfreq_mhz· number · optionnel
Frequency in megahertz (MHz)wavelength_m· number · optionnel
Wavelength in metres
Exemple d'appel{"name": "wavelength_freq", "arguments": {"freq_mhz": 1, "wavelength_m": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"freq_ghz": 1, "freq_mhz": 1, "wavelength_m": 1, "wavelength_cm": 1, "wavelength_ft": 1, "wavelength_mm": 1}} - wire_ampacity≈ 1026 tokens
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.
Paramètres, retour & exemple (6)
Paramètresconductor· string · optionnel · copper | aluminum
Conductor material. Copper has higher ampacity; aluminum is lighter and cheaper for large feeders.insulation· string · optionnel · 60 | 75 | 90
Insulation temperature rating in °C. 60=TW/UF-B, 75=THW/THWN/XHHW (most common), 90=THHN/THWN-2.current_amps· number · requis
Required circuit current in amperes. Use 125% of continuous load per NEC 210.20(A).ambient_temp_c· number · optionnel
Ambient temperature in °C. NEC base is 30°C. Higher temps require derating. Typical: 30 (indoor), 40 (attic/hot), 45+ (rooftop conduit).continuous_load· boolean · optionnel
Whether the load operates continuously (3+ hours). NEC requires 125% sizing for continuous loads. Set false for intermittent loads.conductors_in_raceway· integer · optionnel
Number of current-carrying conductors in a single raceway or cable. More than 3 requires derating per NEC 310.15(C)(2).
Exemple d'appel{"name": "wire_ampacity", "arguments": {"current_amps": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"all_gauges": [], "minimum_awg": 1, "base_ampacity_a": 1, "insulation_label": "texte", "minimum_awg_label": "texte", "ambient_correction": 1, "derated_ampacity_a": 1, "required_ampacity_a": 1, "conductor_count_correction": 1}} - wire_gauge≈ 617 tokens
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.
Paramètres, retour & exemple (5)
Paramètresvoltage· number · requis
System voltage (V)conductor· string · optionnel · copper | aluminum
Conductor material: copper or aluminumdistance_m· number · requis
One-way conductor distance in meterscurrent_amps· number · requis
Load current in amperes (A)max_drop_pct· number · optionnel
Maximum allowable voltage drop as percentage (default 3%)
Exemple d'appel{"name": "wire_gauge", "arguments": {"voltage": 1, "distance_m": 1, "current_amps": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"insufficient": true, "actual_drop_v": 1, "wire_area_mm2": 1, "actual_drop_pct": 1, "recommended_awg": 1, "resistance_per_m": 1, "recommended_awg_label": "texte"}} - wireguard_mtu≈ 572 tokens
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.
Paramètres, retour & exemple (3)
Paramètresipv6· boolean · optionnel
Whether the outer (transport) IP header uses IPv6 (40 bytes) instead of IPv4 (20 bytes)over_pppoe· boolean · optionnel
Whether the link uses PPPoE encapsulation (adds 8 bytes of overhead)interface_mtu· integer · optionnel
MTU of the underlying physical or virtual network interface in bytes
Exemple d'appel{"name": "wireguard_mtu", "arguments": {"ipv6": true, "over_pppoe": true, "interface_mtu": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"breakdown": {}, "wireguard_mtu": 1, "overhead_bytes": 1}} - zfs_capacity≈ 584 tokens
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.
Paramètres, retour & exemple (5)
Paramètresraid_type· string · optionnel · stripe | mirror | raidz1 | raidz2 | raidz3
ZFS RAID level: stripe (no redundancy), mirror (2-way), raidz1/2/3 (single/double/triple parity)disk_count· integer · requis
Total number of physical disks in the pooldisk_size_tb· number · requis
Size of each individual disk in terabytesrecord_size_kb· number · optionnel
ZFS record size in kilobytes, affects compression and performancemetadata_overhead_pct· number · optionnel
Percentage of raw capacity consumed by ZFS metadata, checksums, and internal structures
Exemple d'appel{"name": "zfs_capacity", "arguments": {"disk_count": 1, "disk_size_tb": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"raw_tb": 1, "usable_tb": 1, "data_disks": 1, "parity_disks": 1, "efficiency_pct": 1}} - zfs_ram≈ 558 tokens
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.
Paramètres, retour & exemple (4)
Paramètresworkload· string · optionnel · general | nas | database | virtualization
Primary workload type: general (mixed), nas (sequential reads/writes), database (random IO), virtualization (mixed random)pool_size_tb· number · requis
Total usable pool size in terabytesdedup_enabled· boolean · optionnel
Whether ZFS deduplication is enabled (significantly increases RAM requirements)l2arc_size_gb· number · optionnel
Size of L2ARC (read cache SSD) in gigabytes; requires additional RAM for index
Exemple d'appel{"name": "zfs_ram", "arguments": {"pool_size_tb": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"notes": "texte", "min_ram_gb": 1, "arc_target_gb": 1, "dedup_table_gb": 1, "recommended_ram_gb": 1}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».