view_simulation_result

Prepare an interactive Y-up browser view of an integrity-verified published simulation_result: VTU/Fluxcore CGNS volume or VTP boundary.

Scope: artifacts:read. Catalogue annotation: Read. Additional ownership and role checks may apply.

REST: POST /v1/artifacts/{artifact_id}/simulation-view.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

mode

"surface" / "section" / "streamlines"

No

"surface"

field_names

array of string or null

No

null

minItems: 1; maxItems: 12; Published scalar fields or vector components/magnitude; omit to discover available fields.

axis

"x" / "y" / "z" or null

No

null

position_m

number or null

No

null

include_edges

boolean or null

No

null

Surface/section views: false omits optional wire edges, retaining every triangle and field value. Omit preserves edges.

seed_points_m

array of array [number, number, number] or null

No

null

minItems: 1; maxItems: 128; Streamlines only: explicit starting XYZ points in the saved volume coordinate frame, in metres.

vector_field

string or null

No

null

pattern: "^[A-Za-z0-9_][A-Za-z0-9_.:-]{0,127}$"; Streamlines only: saved velocity vector array, defaults to U. Scalar magnitude is not a vector.

integration_direction

"forward" / "backward" / "both" or null

No

null

Streamlines only: integration direction; defaults to forward.

max_length_m

number or null

No

null

maximum: 1000000; exclusiveMinimum: 0; Streamlines only: required maximum traced length in metres, at most 1,000,000 m.

max_steps

integer or null

No

null

minimum: 1; maximum: 4000; Streamlines only: maximum integration steps per trace; defaults to 2000, at most 4000.

artifact_id

string (uuid)

Yes

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