mcp: the solve tool runs nonlinear and buckling steps too, and its docs list heat

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01UhhZMBTviDQxZvwnyP89fo

crates/mcp/src/server.rs

@@ -29,7 +29,7 @@ forces in N); Z is up. A typical analysis: `open` a .solidcraft design (or a .fi
 .3mf); `inspect_model` for its bodies and their persistent face names; `mesh` (method tet: {body, tolerance}); \
 then `execute` the model definition commands (model.set.create {name, geometry: [{body, face}]}, \
 model.material.create, model.section.create, model.boundary_condition.create, model.load.create, model.step.create \
-— list_commands shows each one's parameters); `check_model`; `solve` (static, frequency, explicit, fluid); \
+— list_commands shows each one's parameters); `check_model`; `solve` (static, nonlinear, frequency, buckle, explicit, fluid, heat); \
 `show_results` (field: displacement, von_mises…; its reply has the field's range) and `probe` / `reactions` for \
 numbers; `screenshot` to look; `save` or `write_deck` (abaqus, nastran, lsdyna). Partitions: geometry.datum makes a \
 datum plane, geometry.partition cuts the design's bodies into cells by it (cut faces partition:<name>:a|b; kept in \

crates/mcp/src/tools.rs

@@ -30,8 +30,15 @@ const MESHERS: &[(&str, &str, &str)] = &[
 ];
 
 /// The analyses the `solve` tool runs; one whose command this build lacks is left out.
-const ANALYSES: &[(&str, &str)] =
-    &[("static", "solve.static"), ("frequency", "solve.frequency"), ("explicit", "solve.explicit"), ("fluid", "solve.fluid"), ("heat", "solve.heat")];
+const ANALYSES: &[(&str, &str)] = &[
+    ("static", "solve.static"),
+    ("nonlinear", "solve.nonlinear"),
+    ("frequency", "solve.frequency"),
+    ("buckle", "solve.buckle"),
+    ("explicit", "solve.explicit"),
+    ("fluid", "solve.fluid"),
+    ("heat", "solve.heat"),
+];
 
 const VIEWS: &[&str] = &["iso", "home", "fit", "front", "back", "top", "bottom", "left", "right"];