submit_study

Run a parameter sweep or design study: submit several geometry, mesh or simulation cases at once with one combined estimate and one budget check.

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

REST: POST /v1/studies.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

kind

"geometry" / "mesh" / "simulation"

Yes

Omitted

study_id

string

Yes

Omitted

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

cases

array of StudyCase

Yes

Omitted

minItems: 1; maxItems: 100

max_concurrent

integer

No

2

minimum: 1; maximum: 16; Most children of this study that run at once (plan limits still apply).

notify_url

string or null

No

null

maxLength: 2048; Public HTTPS URL notified as each child finishes.

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