validate_simulation

Validate the RANS, URANS or CHT input contract without compute.

Scope: simulations:write. Catalogue annotation: Read. Additional ownership and role checks may apply.

REST: POST /v1/simulations/validate.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

project_id

string (uuid) or null

No

null

mesh_artifact_id

string

Yes

Omitted

minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$"

restart_artifact_id

string or null

No

null

minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_-]+$"

mesh_unit_conversion

MeshUnitConversion or null

No

null

config

MCP_validate_simulation_FluxCoreConfig

No

Omitted

decision_context

MCP_validate_simulation_DecisionContext

No

Omitted

convergence_criteria

MCP_validate_simulation_ConvergenceCriteria or null

No

null

How to judge this run converged when it finishes; omit for the standard test.

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": "validate_simulation",
    "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.