run_job
Create a Task handle for MCP Tasks with a stable client_request_id so lost creation responses are safe to retry.
Instructions
MCP Tasks compatibility entry point for explicitly creating a Task handle.
A client declaring io.modelcontextprotocol/tasks receives a Task handle immediately. Older clients block and receive the ordinary final tool result. The stable client_request_id makes a lost creation response safe to retry.
Do not choose this for ordinary command execution: use run. Do not choose it for generic asynchronous submission or fan-out: use submit_job. Only retry a lost Task creation with the same client_request_id and identical arguments.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"command": "<command>",
"client_request_id": "<client_request_id>"
},
"name": "run_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | ||
| env | No | ||
| host | No | ||
| name | No | ||
| queue | No | ||
| backend | No | ||
| command | Yes | ||
| artifacts | No | ||
| resources | No | ||
| capture_logs | No | ||
| slurm_options | No | ||
| timeout_seconds | No | ||
| client_request_id | Yes | ||
| stall_timeout_seconds | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||