sim_get_readiness
Audit schematic components for SPICE simulation readiness, classifying each as ready, needing a primitive, or requiring a vendor model file before simulation.
Instructions
Audit every component on the active schematic for SPICE readiness.
Use this as step 1 of any simulation workflow. The response classifies each component into one of three buckets:
ready, SpicePrefix already set; nothing to do.needs_primitive, a passive (R/L/C) or source (V/I/D/Q) that just needs SpicePrefix + Value. Pass them all to sim_attach_primitives in one call.needs_file, an IC or active part that requires a manufacturer-supplied .mdl / .ckt / .lib file. Call sim_attach_model after fetching the file from the vendor.
CRITICAL, vendor SPICE models only:
Never fabricate a SPICE model from datasheet reasoning. The
parameters that matter for convergence, bias point, and
small-signal behavior are not in any datasheet summary; a
plausible-looking hand-rolled model produces confidently-wrong
simulation results. The response's _spice_guidance block
makes this rule explicit and gives you per-part search queries.
Returns: Dict with: - ready, ready_count - needs_primitive, needs_primitive_count (each entry has designator, comment, suggested_prefix, suggested_value) - needs_file, needs_file_count (each entry has designator, comment, lib_ref, manufacturer, manufacturer_part) - _spice_guidance (rules + structured search_hints + primitive_hints)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||