predict_physics

Get a fast PhysicsAI estimate of thermal or flow performance for a design, in seconds, instead of a full CFD run.

Scope: predictions:write. Catalogue annotation: Writes / prepares / submits work. Additional ownership and role checks may apply.

REST: POST /v1/predictions.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

project_id

string (uuid) or null

No

null

model_id

string

Yes

Omitted

minLength: 1; maxLength: 100; pattern: "^[A-Za-z0-9][A-Za-z0-9._-]*$"

model_version

string

Yes

Omitted

minLength: 1; maxLength: 100; pattern: "^[A-Za-z0-9][A-Za-z0-9._-]*$"

geometry_artifact_id

string

Yes

Omitted

minLength: 1; maxLength: 100; pattern: "^[A-Za-z0-9][A-Za-z0-9._-]*$"

conditions

ElectronicsConditions

No

Omitted

include_fields

boolean

No

true

idempotency_key

string

Yes

Omitted

minLength: 1; maxLength: 128; pattern: "^[A-Za-z0-9_.:-]+$"; Use a fresh unique key for each newly requested job, even with identical inputs or a matching completed job. Reuse unchanged only for retries/resuming that same intended job. Never replace it to retry an uncertain submission.

notify_url

string or null

No

null

maxLength: 2048; Optional public HTTPS URL that receives a signed notification when the job finishes, so you need not poll.

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