MagicON RF Design Engines

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

TX/RX/T-R chains, OTA link, radar, PCB filters, patch antennas, stackup, thermal, PDN, compliance.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "MagicON RF Design Engines": {
      "url": "https://api.pcbgenerator.com/mcp/",
      "transport": "streamable-http"
    }
  }
}

Measured tools (17)

• design_rf_chain read-only

  Design a complete RF transmitter chain with the convergent orchestrator: selects the driver, PA, filter, and connector (the signal source is the user's input power by default — no VCO unless one is explicitly the generator), matches drive power between stages, inserts a pre-driver or attenuator when needed to reach the target output power, and returns the BOM plus a convergence summary (achieved vs target output). When the BOM's pricingCoverage is 'partial', total_usd is a subtotal of pricedLines of totalLines parts: never call it the total, and state no figure for the unpriced parts. For a receiver, use design_rf_receiver instead. For a module that shares one antenna between transmit and receive, use design_tr_module instead.

  Parameters:

  • frequency (required) — number — Operating frequency in GHz (scalar).
  • target_output_power (required) — number — Target transmitter output power in dBm.
  • region — string — Target market / regulatory region (e.g. 'USA', 'Europe', 'Global'). Set it when the user states their market so the design-time power clamp can enforce the right limits — an EU/Europe design with a known antenna gain is held to the ETSI e.i.r.p. limit (EN 300 328 / EN 301 893), not just the FCC ISM conducted limit.
  • bandwidth — number — Signal bandwidth in MHz (optional).
  • application — string — Application context (e.g. satcom_c_band, 5g_cellular, wifi_wlan). Defaults to 'general'. For a drone, send the most specific link the user names: drones_digital_video (digital/OFDM video: the PA is judged on LINEAR power), drones_analog_video (analog FM video: saturated power, plus the FCC 15.249 licence note) or drones_control_telemetry; plain 'drones' means the modulation is unknown (the PA is judged on P1dB).
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • input_power_dbm — number — The power the user's radio or signal source delivers into the chain, in dBm (e.g. 0 or -10), ONLY when the user states it. It is the INPUT, never the target output. Omit it when not stated — the result then says which level was assumed.
  • protected_bands — array — Bands another radio on the same platform listens on (e.g. a drone's GNSS receiver), checked against the filters after the PA. Only when the user asks to protect a band. A cited ITU RNSS band is named by source ('table:rnss_1164_1215', 'table:rnss_1215_1240', 'table:rnss_1240_1300', 'table:rnss_1559_1610', 'table:rnss_5010_5030') and needs no edges; a band the user states uses source 'user' with name, fLowHz and fHighHz. requiredRejectionDb ONLY when the user states it — it narrows the filter choice. Never invent an edge or a requirement.
  • antenna_gain_dbi — number — Antenna gain in dBi. Set it when the user states their antenna so an EU/ETSI design can enforce the e.i.r.p. limit at the real gain (conducted ceiling = e.i.r.p. limit − antenna gain); without it the ETSI clamp does NOT engage (no 0 dBi assumption is made in the design).
  • board_mount_only — boolean — true ONLY when the user asks for board-mount (surface-mount) parts only. The PA, driver, predriver and the isolator after the PA then skip parts whose record says drop-in, flange, die or cable; if none is left the slot stays empty and the warnings say why. The VCO, attenuator, filter and coupler slots are not filtered.
  • harmonic_2nd_dbc — number — The 2nd-harmonic limit at the output in dBc (a negative number, e.g. -40), ONLY when the user states one. The filters after the PA are then chosen and judged against it. Never guess it and never derive it from a regulation.
  • hopping_channels — integer — Drone control/telemetry only: the number of hopping channels the link uses, WHEN THE USER STATES IT. 50 or more lifts the design ceiling from FCC 15.247(b)(2)'s 24 dBm to 30 dBm. Never guess it.
  • digital_modulation — boolean — Drone control/telemetry only: true WHEN THE USER STATES the link uses digital modulation (FCC 15.247(b)(3)), which lifts the 24 dBm ceiling to 30 dBm. Never guess it.
  • input_voltage_max_v — number — Highest voltage the board supply reaches, in volts (optional; e.g. a fully charged battery). Only when the user STATES it. Pair with input_voltage_min_v.
  • input_voltage_min_v — number — Lowest voltage the board supply reaches, in volts (optional; e.g. a battery at cut-off). Only when the user STATES it — never derive it from a cell count or chemistry. Give it together with input_voltage_max_v and a main_board_input_voltage inside the two; the power tree then picks regulators that work across the whole span.
  • transmit_bias_pulsed — boolean — Pulsed designs only: true when the user says the amplifier bias (gate or drain) is switched off between pulses, false when it stays on. Omit when not stated — the idle draw between pulses is then counted as heat.
  • internally_matched_only — boolean — Prefer internally 50-ohm matched parts (optional). A preference, not a filter: an unmatched PA can still win on score, and the result's warnings then say so.
  • main_board_input_voltage — number — Board DC supply voltage in volts that the power tree steps down/up to the per-component rails (optional; defaults to 12 V). Set it when the user states their supply rail, e.g. a 28 V or 48 V bench/battery input.
  • transmit_duty_cycle_percent — number — Transmit duty cycle in percent for a PULSED system (radar). Default 100 = continuous wave (CW). Set it to the real duty (e.g. 10 for a 10% radar) so thermal, stress, and compliance use AVERAGE power, not peak.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• design_rf_receiver read-only

  Design or analyse a superheterodyne RECEIVER. Selects catalog parts for each slot (limiter, LNA, image filter, mixer, LO, IF filter, IF amp, step attenuator) and returns the frequency plan (image, half-IF, LO leakage), the cascaded noise figure, noise floor, MDS, sensitivity, SFDR and dynamic range, plus the ADC interface (sample rate, Nyquist zone, ENOB, jitter limit). Pass rfFrequencyHz to design one; pass stages[] only for a bench receiver the user described with their own numbers. For a transmitter, use design_rf_chain instead. For a module that shares one antenna between transmit and receive, use design_tr_module instead.

  Parameters:

  • ifHz — number — Intermediate frequency in Hz. Omit to let the server choose one and disclose that it did.
  • loSide — string — LO above or below the RF. Omit to let the server pick.
  • stages — array — Explicit receive chain, ONLY for a bench receiver the user described with their own numbers. Do not hand-build this from memory — pass rfFrequencyHz instead and let the server select real parts.
  • targets — object — Requirements the user stated, judged pass/fail in the result's validation. Keys: noiseFigure, sensitivity, mds, noiseFloor, imageRejection, sfdr, instantaneousDynamicRange, iip3, rxGain, rxGainMax. Each value is a number or {min, typ, max}. Only values the user gave; never invent one.
  • application — string — Application context, the same label design_rf_chain takes (e.g. drones, marine_radar, wifi_wlan). Every part is scored for it; free text is resolved to the nearest known label, and one that cannot be resolved is scored as 'general' with a warning saying so. Omit for 'general'.
  • bandwidthHz — number — Receiver noise bandwidth in Hz. Required for noise floor, MDS and sensitivity — omit it and those are reported as unavailable rather than assumed.
  • architecture — string — front_end_only for a radio built on an integrated transceiver (drones): selects only limiter, preselector and LNA, ending at the transceiver input. Omit for a full superheterodyne.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • inputPowerDbm — number — Signal level at the antenna port, in dBm. Omit for a small-signal reference, which the result discloses.
  • requiredSnrDb — number — SNR needed at the demodulator, in dB.
  • rfFrequencyHz — number — RF centre frequency in Hz (e.g. 9.4e9 for X-band).
  • transceiverNfDb — number — The transceiver's own noise figure in dB, front_end_only only. Omit it and system NF, MDS and sensitivity are withheld, never assumed.
  • main_board_input_voltage — number — Board DC supply voltage in volts, the same argument design_rf_chain takes. This tool returns no bill of materials or power tree, so a value given here is reported back as unused rather than applied.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• design_tr_module read-only

  Design a T/R (transmit/receive) module that shares ONE antenna between a transmitter and a receiver. Designs both chains through the existing engines, selects the shared front end (a T/R switch, or a circulator with a receive-path limiter), and returns four safety budgets: TX-to-RX isolation against the receiver's damage limit, the receive window left after switching and limiter recovery (with the blind range: the closest echo the receiver can hear), limiter leakage driving the LNA into compression, and transmit power against each part's survivability rating. Pass frequencyGhz and targetOutputPowerDbm to design one; pass txPeakPowerDbm and isolationDb only to check a front end the user already described with their own numbers. For a transmitter alone, use design_rf_chain instead. For a receiver alone, use design_rf_receiver instead.

  Parameters:

  • prfHz — number — Pulse repetition frequency in Hz, for a pulsed system. Omit and the switching/blanking budget is absent, not assumed.
  • topology — string — Shared-antenna element. Omit to use tr_switch, which the result discloses. Choose circulator_limiter for high transmit power — if the stress budget reports over_limit for a switch, re-run with this. switch_and_circulator belongs to architecture array_element only (and is its only topology); any other pairing is refused.
  • application — string — Application context, the same label design_rf_chain takes (e.g. drones, marine_radar, wifi_wlan). Every part is scored for it; free text is resolved to the nearest known label, and one that cannot be resolved is scored as 'general' with a warning saying so. Omit for 'general'.
  • bandwidthHz — number — Receiver noise bandwidth in Hz.
  • isolationDb — number — Transmit-to-receive isolation in dB, for the explicit-inputs path only.
  • pulseWidthS — number — Transmit pulse width in seconds (e.g. 1e-6).
  • architecture — string — front_end_only for a radio built on an integrated transceiver (drones): selects only limiter, preselector and LNA, ending at the transceiver input. array_element for ONE element of a phased array, beamformer port to antenna port: phase shifter + step attenuator shared by both paths, a low-power T/R switch and a circulator; requires beamformerDriveDbm. Omit for a full superheterodyne.
  • frequencyGhz — number — Operating frequency in GHz (e.g. 9.4 for X-band).
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • antennaFilter — boolean — array_element only: true to add a shared bandpass filter between the circulator and the antenna, charged to both paths. Off unless the user asks for it.
  • requiredSnrDb — number — SNR needed at the demodulator, in dB.
  • beamformerNfDb — number — array_element only: the beamformer's own noise figure behind the common leg, in dB. Omit it and the system noise figure at the beamformer port is withheld.
  • txPeakPowerDbm — number — Peak transmit power AT THE ANTENNA PORT, in dBm. Pass this ONLY to check a front end the user already has — it skips design entirely. To design a module, pass targetOutputPowerDbm instead.
  • transceiverNfDb — number — The transceiver's own noise figure in dB, front_end_only only. Omit it and system NF, MDS and sensitivity are withheld, never assumed.
  • beamformerDriveDbm — number — array_element only: the input power at the beamformer port, in dBm, as the user stated it. Required for an array element — never assumed; the tool refuses and names it when absent.
  • minDetectionRangeM — number — The closest target the user must detect, in metres, when they state one. Checked against the blind range (pulse width + switch back to receive + limiter recovery). Needs prfHz and pulseWidthS; omit when not stated — no requirement is assumed.
  • transmitBiasPulsed — boolean — Pulsed designs only: true when the user says the transmit amplifier bias (gate or drain) is switched off between pulses, false when it stays on. Omit when not stated — the idle draw between pulses is then counted as heat, and the thermal disclosures say so.
  • antennaReturnLossDb — number — Antenna return loss in dB. Without it the antenna-mismatch leakage path assumes a 1.5:1 VSWR (13.98 dB) and says so.
  • maxTxGainFlatnessDb — number — The user's transmit gain flatness requirement across the band, in dB. Not computed; reported as not evaluated with the reason. Omit when not stated.
  • minTxToRxIsolationDb — number — The user's required TX-to-RX isolation in dB (e.g. 40 for '> 40 dB'). Judged against the shared part's own isolation and reported under requirements. Not the same as isolationDb. Omit when not stated.
  • targetOutputPowerDbm — number — Transmit output power the chain is designed to, in dBm (20 W = 43 dBm). Required — every safety budget is measured against it and no default is substituted.
  • maxUnblankingRecoveryS — number — The user's maximum unblanking (receiver) recovery time in seconds (e.g. 100e-9 for '< 100 ns'). Judged against the switch back to receive plus limiter recovery. Omit when not stated.
  • maxPulseToPulsePhaseDeg — number — The user's pulse-to-pulse phase stability requirement in degrees. Not computed; reported as not evaluated with the reason. Omit when not stated.
  • main_board_input_voltage — number — Board DC supply voltage in volts that the power tree steps down/up to the per-component rails (optional; defaults to 12 V). Set it when the user states their supply rail, e.g. a 14.8 V 4S battery or a 28 V bench input. Same meaning as on design_rf_chain.
  • transmitDutyCyclePercent — number — Transmit duty cycle in percent (e.g. 10 for a 10% pulsed radar). Selects each part's PULSED survivability rating instead of its CW rating, which for a limiter is commonly 7 dB higher. Omit for continuous wave — the CW rating is then used, and a part declaring no pulsed rating keeps its CW one with that substitution disclosed. Redundant if prfHz and pulseWidthS are both given, which imply it.
  • maxPulseToPulseAmplitudeDb — number — The user's pulse-to-pulse amplitude stability requirement in dB. Not computed; reported as not evaluated with the reason. Omit when not stated.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_link_budget read-only

  Compute a cascaded RF link budget. For the chain just designed, call with NO arguments — the server derives stages and input power from the design. Pass stages + inputPowerDbm only for a bench/hypothetical chain. Returns per-stage output power, cumulative gain, Friis cascaded NF, gain-referred reciprocal-sum cascaded OIP3, P1dB headroom warnings, and overall risk. Optionally pass bandwidthHz (and requiredSnrDb) to also get the receiver noise floor, MDS, sensitivity, SFDR, and instantaneous dynamic range. For a link through the air between two antennas (EIRP, path loss, range), use run_ota_link instead.

  Parameters:

  • stages — array — Ordered list of RF stages for a bench/hypothetical chain. Omit for a just-designed chain (derived server-side). Each stage may declare gainDB or lossDB (loss is treated as -|lossDB|), nfDB, oip3Dbm, p1dbDbm, and an authoritative outputPowerDbm that snap-seeds the cascade. Mark a mixer with mixerRole, plus nfSideband when the user or datasheet says which definition its nfDB uses.
  • bandwidthHz — number — Optional receiver noise bandwidth in Hz. When given, the result adds the thermal noise floor, MDS, SFDR, and instantaneous dynamic range (a receiver figure of merit).
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • inputPowerDbm — number — Input power into the first stage, in dBm. Omit for a just-designed chain (derived from its power flow).
  • requiredSnrDb — number — Optional SNR (dB) required for detection/demod. With bandwidthHz, yields receiver sensitivity = MDS + this SNR.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_stackup_solver read-only

  Run the impedance-aware stackup constraint solver to find optimal PCB configurations. Use when the user wants ranked material/thickness/copper solutions for a given layer count and frequency. Returns scored and ranked feasible stackups. Each solution's prepreg_thickness_mm is ONE prepreg layer: prepreg_sheets (1-3) x prepreg_sheet_thickness_mm (maker's table). Per-layer numbers do NOT sum to total_thickness_mm — the total uses the pressed thickness, 0.04064 mm thinner per layer. Report both as returned; never 'correct' one to match the other.

  Parameters:

  • layer_count (required) — number — Total copper layers (even number, 2-32)
  • frequency_ghz (required) — number — Operating frequency in GHz
  • topology — string — Transmission line type: microstrip or stripline (default microstrip)
  • build_type — string — Lamination build: 'single' (default) or HDI level hdi1-hdi4. HDI defaults cost_priority to performance.
  • solder_mask — object — Solder mask covering the OUTER trace, as {thickness_mm, dk}. Mask raises the effective permittivity around the trace and pulls Z0 down, so the solver returns a NARROWER width for the same target impedance. OMIT IT (the default) and the microstrip is solved BARE — pass it only when the user says the outer traces are mask-covered, or states a mask thickness or mask Dk. Applies to microstrip targets only: a stripline is buried under laminate, not mask. Both members are optional and default to typical green LPI (0.02 mm, Dk 3.5); thickness_mm must be over 0 and at most 0.2, dk over 1 and at most 10. Mask LOSS is not modeled: the insertion-loss score leaves it out, and a masked result says so in diagnostics — tell your user when you cite a masked solve.
  • construction — string — Lamination. OMIT it unless the user named one: an omitted lamination is built foil; naming a core material builds core_outer where it can be (4+ layers, build_type 'single'), whatever the frequency. 'foil' puts prepreg outermost, so an outer microstrip rides on prepreg; 'core_outer' puts a core outermost, so the core material, such as an RF laminate, sits directly under the outer microstrip — the same choice Guided Phase IV offers. 'auto' searches BOTH and ranks them together; send it only when the user asks to compare the two. On 6+ layers, naming a core outside the FR-4 grades (e.g. RO4350B) under core_outer ALSO searches hybrid boards: that core on the two outer cores, an FR-4 grade on the cores between (a hybrid solution names its inner_core_material); the other boards have every core that material. No hybrid with a stripline target. Each solution reports the construction it was built as; name it when you cite that solution.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • cost_priority — string — Cost preference: low, balanced, or performance. Default balanced; an HDI build_type OR a frequency at or above 18 GHz defaults to performance instead, because at mm-wave a balanced weighting ranks an FR4-class laminate above every low-loss one. Pass it explicitly to override either default — a stated preference always wins. The priority actually used comes back as costPriority.
  • input_power_w — number — RF power in W going into the line, ONLY when the user states one (0-10000; needs line_length_mm). Adds heat_w: the watts the line turns into heat.
  • max_solutions — number — Max solutions to return, 1-20 (default 5)
  • impedance_ohms — number — Target impedance in Ohms (default 50). Single-target convenience — ignored when impedance_targets is given.
  • line_length_mm — number — Length of the line in mm, ONLY when the user states one (0-2000). Each single-ended trace always returns its loss in dB/mm (trace_results[].loss); with a length it also returns line_loss_db for that line.
  • reflow_process — string — Assembly reflow process; enforces a Tg floor on all dielectrics (default lead_free).
  • copper_weight_oz — number — Restrict solutions to this copper weight in oz (0.5, 1, 2, or 3). Omit to let the solver optimize copper weight; an omitted value inherits the latest update_stackup_config copper weight automatically. The value is the FINISHED thickness, with outer-layer plating already included (1 oz = 0.035 mm finished, plated up from 0.5 oz starting foil). A spec written as '0.5 oz base foil + plating, 1.7 mil finished' uses the OTHER convention — pass 1, not 0.5.
  • impedance_targets — array — Up to 4 impedance targets the stackup must satisfy SIMULTANEOUSLY, each {ohms, topology ('microstrip'|'stripline'), differential (bool), spacing_mm (differential pair gap in mm, default 0.15)}. Use for multi-impedance boards — e.g. 50 ohm RF plus a 100 ohm differential pair. Overrides impedance_ohms/topology.
  • target_thickness_mils — number — Board thickness in mils (default 62)
  • allowed_core_materials — array — Restrict core dielectrics to these catalog materials (e.g. RO4350B, MEGTRON6; 'FR4' = the standard FR-4 grades). Pass ONLY materials the user named; omit for the full catalog.
  • thickness_tolerance_mm — number — Allowed deviation from the target thickness in mm. OMIT it and the solver uses 10% of the target thickness. Set it only when the user states a tolerance. The value the solve used comes back as thicknessToleranceMm - cite that one.
  • allowed_prepreg_materials — array — Restrict prepregs to these catalog materials (e.g. RO4450F, MEGTRON6; 'FR4' = the standard FR-4 grades). Pass ONLY materials the user named; omit for the full catalog.
  • allowed_inner_core_materials — array — For a HYBRID board (an RF core on the two outer cores, a cheaper laminate on the cores between them): the catalog materials the inner cores may be. Omitted, they are 'FR4' (the standard FR-4 grades). Pass ONLY what the user named for the inner cores; giving it also asks for hybrids.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_thermal_analysis read-only

  Run a full PCB thermal analysis: via array Rth, junction-to-ambient stack, Kennedy spreading, Coffin-Manson barrel stress, Timoshenko warpage, and resin-flow estimation. Mirrors POST /api/stackups/{id}/thermal-analysis. Call with no arguments once a design exists: the server takes power_w from the designed chain's dissipated power and defaults ambient_c to 25 C. The result carries `recommendations` (thermal vias, copper, plating) — answer adjustment questions from those entries. If the user states a heatsink or airframe spreader, pass `heatsink` (θcs, θsa and mount, all three as stated — never guessed); Tj is then computed through it instead of still-air convection.

  Parameters:

  • heatsink — object — Optional user-STATED heatsink (or drone airframe spreader) the part is mounted to. ALL THREE properties are required together and NONE is ever defaulted — if the user has not stated one, ask; a partial object is rejected naming the missing field. When given it REPLACES still-air convection; the result echoes it with source 'user_supplied' and a heat_path.
  • delta_t_c — number — Thermal-cycling ΔT in °C for Coffin-Manson fatigue analysis (e.g. 100 °C from −40 to +60 °C operating swing).
  • via_config — object — Optional thermal via array. ALL SEVEN properties are required together — a partial object is rejected — and plating_thickness_mm must be < via_diameter_mm / 2.
  • layer_count — integer — Total copper layer count (even number, typically 2–32). Used to scale per-layer thermal contributions.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • pour_area_mm2 — number — Total copper-pour spreader area in mm² on the heat-sink side; larger pours reduce the spreading-Rth term.
  • analysis_input — object — Optional once a design exists. {power_w, ambient_c} are BOTH optional: the server fills power_w from the designed chain's dissipated power and defaults ambient_c to 25 C. Omit this entirely to run thermal on the current design.
  • board_width_mm — number — Overall PCB width in mm (warpage / CTE inputs).
  • stackup_layers — array — Optional per-layer thermal contributions.
  • board_length_mm — number — Overall PCB length in mm — used for Timoshenko warpage and CTE-mismatch curvature estimates.
  • source_area_mm2 — number — Heat source footprint area in mm² — typically the IC die or package pad footprint. Used for Kennedy spreading resistance.
  • theta_jc_c_per_w — number — Device junction-to-case thermal resistance in °C/W (datasheet R_θJC). Optional — the server derives it from the designed chain's PA record when available.
  • copper_thickness_mm — number — Plane/pour copper thickness in mm (e.g. 0.035 for 1 oz, 0.070 for 2 oz). Drives the lateral spreading conductance.
  • effective_cte_z_ppm — number — Effective z-axis CTE in ppm/°C — input to Coffin-Manson barrel-stress life estimation. Typical 40–70 ppm/°C for FR4.
  • copper_coverage_top_pct — number — Fractional copper coverage on the top side (0–100 %). Used for warpage symmetry and effective-CTE calculations.
  • copper_coverage_bottom_pct — number — Fractional copper coverage on the bottom side (0–100 %). Asymmetry vs. top drives warpage predictions.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_pdn_analysis read-only

  Run a PDN (power delivery network) impedance analysis: interplanar plane-pair capacitance, multi-cap decoupling impedance vs. target impedance, violations, and recommended decoupling caps. Reuses the Phase-25 engine behind POST /api/pdn/analyze. Inputs are derived server-side from the solved stackup, the BOM's PDN passives, and the power-tree rail — call with no arguments once a design exists.

  Parameters:

  • target — object — Optional target-impedance config {voltage_v, ripple_pct, transient_current_a, rise_time_ns} or {preset_name}. Derived from the power-tree rail when omitted.
  • plane_pairs — array — Optional. Power/ground plane pairs. Derived from the solved stackup when omitted.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • decoupling_caps — array — Optional. Decoupling capacitors. Derived from the BOM's PDN passive lines when omitted.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_compliance_analysis read-only

  Audit the solved stackup against PCB standards (IPC-2221, IPC-6012, IPC-4101, MIL, UL-94, RoHS, REACH): per-rule pass/fail with severities and remediation. Reuses the engine behind POST /api/compliance/check. Layers are derived from the solved stackup and standards default to IPC-2221 + IPC-6012 Class 2 — call with no arguments once a stackup exists.

  Parameters:

  • layers — array — Optional. Stackup layers. Derived from the solved stackup when omitted.
  • standards — array — Optional. Standards to check (e.g. IPC_2221, IPC_6012_CLASS3, ROHS_3, ETSI_EN_300_328, ETSI_EN_301_893) or a region name for advisory reference limits (e.g. 'China', 'SRRC', 'Japan', 'Canada'). Defaults to IPC-2221 + IPC-6012 Class 2 when omitted.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • stackup_config — object — Optional stackup config (layer_count, total_thickness_mm). Derived when omitted.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_ota_link read-only

  Compute a one-way over-the-air link budget — EIRP, free-space path loss (Friis), received power, link margin against receiver sensitivity, a closes/marginal/fails verdict, and the maximum range — using the SAME engine behind POST /api/ota-link/compute. Receiver sensitivity is reused from a prior link budget and transmit antenna gain/frequency from a prior antenna design when not given. FREE-SPACE ONLY: excludes rain, terrain, multipath and fading beyond the misc-loss and fade-margin inputs. Distance and misc loss are user assumptions, disclosed on the result. For the stage-by-stage cascade through one chain's parts (gain, noise figure, OIP3), use run_link_budget instead.

  Parameters:

  • rxNfDb — number — Receiver noise figure (dB) — used to derive sensitivity when none is available.
  • txPowerW — number — Transmit power in WATTS (pass 0.1 for 100 mW). PREFER this for W/mW inputs — the server converts to dBm. Do NOT convert yourself.
  • distanceM — number — Link distance in METRES (pass 5000 for 5 km). USER ASSUMPTION.
  • rxGainDbi — number — Receive antenna gain (dBi). Defaults to 0 (isotropic) — pass it when the far-end antenna is known.
  • txGainDbi — number — Transmit antenna gain (dBi). Reused from a prior patch-antenna design if omitted.
  • miscLossDb — number — Misc/implementation loss lump (dB): cables, connectors, pointing, polarization. USER ASSUMPTION. Default 0.
  • txPowerDbm — number — Transmit power in dBm. Use ONLY when the user states dBm; otherwise pass txPowerW. Wins if both are given.
  • bandwidthHz — number — Receiver noise bandwidth (Hz) — used to derive sensitivity.
  • fadeMarginDb — number — Fade margin required for the link to count as closing (dB). Default 0.
  • frequencyGhz — number — Carrier frequency (GHz). Reused from a prior antenna design if omitted.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • requiredSnrDb — number — Demodulation SNR required (dB) — used to derive sensitivity.
  • sensitivityDbm — number — Receiver sensitivity (dBm). Reused from a prior link budget if omitted.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_radar_performance read-only

  Compute radar performance — the monostatic range equation (received power, SNR vs range, maximum detection range, coherent/non-coherent integration gain) and pulsed-waveform relations (duty cycle, unambiguous range/velocity, range resolution, blind speeds) — using the SAME engine behind POST /api/radar/performance. Antenna gain enters as a dBi number; the detection floor is reused from a prior link budget's MDS when not given. RCS, target range, and system loss are user assumptions, disclosed on the result.

  Parameters:

  • prfHz — number — Pulse repetition frequency (Hz).
  • rcsM2 — number — Target radar cross-section (m^2). USER ASSUMPTION.
  • mdsDbm — number — Detection floor (dBm). Reused from a prior link budget if omitted.
  • gainRxDbi — number — Receive antenna gain (dBi); defaults to gainTxDbi (monostatic).
  • gainTxDbi — number — Transmit antenna gain (dBi).
  • peakPowerW — number — Transmit peak power in WATTS (pass 1000 for 1 kW). PREFER this for W/kW/MW inputs — the server converts to dBm. Do NOT convert to dBm yourself.
  • pulseWidthS — number — Pulse width tau (s).
  • frequencyGhz — number — Carrier frequency (GHz).
  • peakPowerDbm — number — Transmit peak power in dBm. Use ONLY when the user states dBm directly; otherwise pass peakPowerW. Wins if both are given.
  • systemLossDb — number — System loss budget (dB). USER ASSUMPTION. Default 0.
  • targetRangeM — number — Target range (m). USER ASSUMPTION.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • requiredSnrDb — number — Detection SNR (dB) used to solve maximum range.
  • integrationMode — string — 'coherent' (+10log10 N) or 'noncoherent' (~6.5log10 N).
  • integrationCount — integer — Pulses integrated (N >= 1). Default 1.
  • compressedBandwidthHz — number — Pulse-compression bandwidth B (Hz); overrides range resolution.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_planar_filter read-only

  Synthesize a passive planar (copper-on-PCB) filter from analytical formulas: stepped-impedance / open-stub low-pass, or parallel-coupled / hairpin band-pass, Chebyshev or Butterworth. Returns per-section line impedances (Z0e/Z0o for coupled sections), width/spacing, quarter-wave lengths, the total occupied board area, a copper footprint, passband markers, a simulated S21/S11 frequency response (response_curve) with modeled insertion loss / return loss / 3-dB bandwidth (response_summary), and accuracy warnings. Reuses the engine behind POST /api/planar-filter/compute (SSOT). Use it to replace a purchased SMT filter with board copper. Interdigital/combline are not implemented.

  Parameters:

  • filter_class (required) — string — Low-pass or band-pass.
  • topology (required) — string — LPF: stepped_impedance or open_stub. BPF: parallel_coupled or hairpin. (interdigital/combline are Tier B — not implemented.)
  • response (required) — string — Prototype response. chebyshev requires ripple_db.
  • order (required) — integer — Filter order N (number of reactive elements), >= 1.
  • z0_ohm (required) — number — System (port) impedance in ohms, e.g. 50.
  • substrate (required) — object — PCB substrate. line_topology 'microstrip' or 'stripline'; material (the laminate the user named) or er (only a Dk the user stated); h_mm (microstrip height) or b_mm (stripline plate spacing); optional t_mm (copper thickness), tan_d, fab_min_spacing_mm.
  • f0_ghz — number — Center frequency in GHz (BPF only).
  • fc_ghz — number — Cutoff frequency in GHz (LPF only).
  • ripple_db — number — Passband ripple in dB (required for chebyshev).
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • fractional_bw — number — Fractional bandwidth 0<Δ<1 (BPF only), e.g. 0.10 for 10%.
  • impedance_extremes — object — Stepped-impedance LPF only: zh_ohm (high-Z line) and zl_ohm (low-Z line). open_stub uses zh_ohm alone.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• design_patch_antenna read-only

  Design a rectangular microstrip patch antenna (and, when both nx and ny are given, a uniform planar array of it) using the Balanis cavity/transmission-line + array-factor model — the SAME engine behind POST /api/antenna/patch/design and the Guided Phase IV antenna panel. The substrate (dk/df/h) derives from the latest solved stackup's outer prepreg dielectric unless dk/df/h_mm are given explicitly. Returns patch dimensions, resonance/bandwidth/gain, and (for an array) beamwidths, pattern cuts, and a grating-lobe check. The designed gain auto-applies to the chain's antennaGainDbi (compliance/SAR) unless apply_gain=false.

  Parameters:

  • frequency_ghz (required) — number — Target resonant frequency f0 (GHz). Required.
  • df — number — Manual substrate loss tangent override.
  • dk — number — Manual substrate dielectric constant override.
  • nx — integer — Array elements along x (width). Requires ny.
  • ny — integer — Array elements along y (length). Requires nx.
  • h_mm — number — Manual substrate height (mm) override.
  • material — string — Substrate material NAME the user gave (e.g. 'FR4', 'FR408', 'RO4350B'). The server resolves Dk/Df — the catalog for a branded grade, a nominal value for generic 'FR4' — and assumes a standard thickness, disclosing both. Pass this instead of dk/df when the user names a material rather than numbers; do NOT invent dk/df yourself.
  • apply_gain — boolean — Auto-apply the designed gain to the chain's antennaGainDbi. Default true.
  • spacing_x_mm — number — Explicit x-axis element spacing (mm); wins over spacing_lambda.
  • spacing_y_mm — number — Explicit y-axis element spacing (mm); wins over spacing_lambda.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • steer_phi_deg — number — Beam-steer azimuth angle (deg), default 0.
  • spacing_lambda — number — Array element spacing as a fraction of lambda0 (default 0.5).
  • steer_theta_deg — number — Beam-steer elevation angle (deg), default 0.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• run_glass_weave_analysis read-only

  Recommend PCB glass-weave (fiber-weave) styles for the current design: ranks catalogued styles by impedance variation and cost for the design frequency and marks the cheapest one meeting the impedance tolerance. Reuses the Phase-24 engine behind POST /api/glass-weave/recommend. Frequency is derived from the solved stackup / RF specs; tolerance and trace width default to stated assumptions — call with no arguments once a design exists.

  Parameters:

  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • frequency_ghz — number — Optional. Design frequency in GHz. Derived from the solved stackup / RF specs when omitted.
  • trace_width_mm — number — Optional trace width in mm (default 0.1, worst-case narrow).
  • is_differential_pair — boolean — Optional. True halves the effective tolerance (differential pairs are more skew-sensitive). Default false.
  • impedance_tolerance_pct — number — Optional impedance tolerance target in percent (default 5).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• lookup_component_by_mpn read-only

  Look up an RF component in the validated catalog by manufacturer part number: the catalog's summary of its headline figures, not the full datasheet. Returns the frequency, power and gain ranges, package, datasheet link, and the headline figures (Psat, P1dB, gain, noise figure, OIP3, insertion and conversion loss, junction-to-case thermal resistance, maximum junction temperature), each with its datasheet page where one is on file. Figures the record lacks are listed as not in the record, and internal estimates are named but never given as numbers. It does NOT hold derating, absolute-maximum ratings, bias, test conditions or footnotes: for those, read the datasheet link. Use this whenever the user names a specific part, so answers come from catalog data rather than recall.

  Parameters:

  • part_number (required) — string — Manufacturer part number to look up (e.g. 'TGA2624-SM', 'ADL5904', 'MAX2871'). Match is exact; the user's shortened form may need the family suffix.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• compare_rf_chains read-only

  Multi-objective RF chain comparison: designs the primary chain with the convergent orchestrator, generates alternative chains by swapping components, scores every variant on cost / size / performance, and returns the ranked list with a Pareto frontier — the same engine as the Guided 'Compare Alternatives' panel (POST /api/rf-chain/design-multi). Call with no arguments after a chain design to compare that design.

  Parameters:

  • weights — object — Objective weights {cost, size, performance}, each 0-1; normalized to sum 1.0. Defaults to balanced.
  • frequency — number — Operating frequency in GHz. Omit to reuse the conversation's designed chain.
  • max_chains — number — Max variants to return (1-20, default 8).
  • application — string — Application context (e.g. satcom_c_band, wifi_wlan). Derived from the frequency band when omitted.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • target_output_power — number — Target output power in dBm. Omit to reuse the conversation's designed chain.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• find_components_by_spec read-only

  Find real parts in the validated catalog that meet a spec: a part type, an operating frequency in GHz, and optional limits (noise figure, gain, P1dB, Psat, OIP3, insertion loss). Returns the matching parts, best first on the first limit, each with its headline figures and the datasheet page for each figure where one is on file, as lookup_component_by_mpn gives them. Parts whose record lacks a limited figure are named as not compared, never counted as matches. Pass only figures your user stated; an untraceable one is refused.

  Parameters:

  • category (required) — string — Part type, e.g. 'lna', 'pa', 'filter', 'mixer'.
  • frequency_ghz (required) — number — Operating frequency in GHz the part must cover.
  • max_results — integer — How many matches to return (default 10, at most 25).
  • min_gain_db — number — Lowest acceptable gain, in dB. Only a limit your user stated.
  • min_oip3_dbm — number — Lowest acceptable oip3, in dBm. Only a limit your user stated.
  • min_p1db_dbm — number — Lowest acceptable p1db, in dBm. Only a limit your user stated.
  • min_psat_dbm — number — Lowest acceptable psat, in dBm. Only a limit your user stated.
  • user_request — string — The end user's own words that prompted this call, verbatim. Used to verify that the figures you pass were stated by your user rather than inferred. Omit it and the results will be labelled caller-asserted.
  • max_noise_figure_db — number — Highest acceptable noise figure, in dB. Only a limit your user stated.
  • max_insertion_loss_db — number — Highest acceptable insertion loss, in dB. Only a limit your user stated.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• check_grounding read-only

  Check a draft passage against the engine results computed in THIS session. It returns every figure no engine produced, and every claim it checks that the results do not support or contradict (for example a solver score called a loss), each in `findings` with the reason. Run it before publishing or handing over a report, fabrication sheet, BOM summary or any other figure-bearing deliverable built from these tools. It computes nothing and adds no evidence — it only reports what the results back. Fix each finding the way its `why` says: quote the engine's own value, call the tool that computes it, correct the wording, or say plainly in the text that the figure is not from a tool.

  Parameters:

  • text (required) — string — The draft passage to check, verbatim. Pass the prose the end user will actually read — including tables and captions, since a figure in a table is a figure. Markdown is fine.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.