plan_mesh¶
Dry run of an external octree mesh: send the create_mesh request (octree_prism.controls, no idempotency_key) and see the domain, sizes, boundary layer, refinement regions, predicted cells and the cores and memory it would get, without meshing.
Scope: meshes:write. Catalogue annotation: Read. Additional ownership and role checks may apply.
REST: POST /v1/meshes/plan.
Arguments¶
Field |
Type / accepted values |
Required |
Default |
Constraints / meaning |
|---|---|---|---|---|
|
string (uuid) or null |
No |
|
|
|
string |
Yes |
Omitted |
minLength: |
|
string (uuid) or null |
No |
|
Explicitly requested new attempt after reviewing this completed mesh job, including quality or resource failures. Use a fresh idempotency key; this records lineage and never restarts the prior execution. |
|
|
Yes |
Omitted |
structured = Cartesian; octree_prism = octree/polyhedral with prism layers; openfoam = legacy engine identifier. Prefer configured octree_prism for generic unstructured requests; preserve explicit methods. Choose delivered file formats separately with export_formats. |
|
array of |
No |
|
minItems: |
|
integer |
No |
|
minimum: |
|
MCP_plan_mesh_StructuredOptions or null |
No |
|
|
|
MCP_plan_mesh_OpenFoamOptions or null |
No |
|
|
|
MCP_plan_mesh_OctreePrismOptions or null |
No |
|
|
|
No |
Omitted |
Calling the tool¶
Use tools/call with this tool’s exact name and an arguments object matching the fields above. Get the complete live schema before supplying advanced controls:
{
"name": "get_tool_schema",
"arguments": {
"name": "plan_mesh",
"include_definitions": false
}
}
Result and continuation¶
Inspect isError and structuredContent. Keep returned job, operation and artifact IDs. A pending operation_id is followed with get_operation; a compute job is followed with get_job. A wait timeout does not cancel work. Follow returned polling intervals and retain the same idempotency key when reconciling the same submission.
See agent workflow, jobs and operations, uploads, results and error recovery for the applicable lifecycle. MCP annotations describe tool behaviour; they are not blanket permission to run paid work or change account state.