status
Check a background job's lifecycle state, timestamps, exit code or signal, and process identity without blocking on its execution.
Instructions
Get the current lifecycle status of a background job started by run: state (starting/running/exited/killed/failed), timestamps, exit_code/signal/diagnostic as applicable. For a job that got a real OS process, also reports its pid together with birth_identity, the SAME identity this server's own kill checks before ever signaling - never the pid alone, since a pid is reusable the instant its process exits. birth_identity.state is one of pending (capture still in flight), captured (a real identity is present, under identity), or unavailable (capture failed, or none was ever attempted). identity itself is platform-tagged: linux-starttime-ticks is an exact kernel start-time counter with no tolerance concept; posix-elapsed (macOS and every other non-Linux POSIX platform) is a real but PROBABILISTIC ps-observed elapsed-time correlation, never a certainty. Either way this only proves which process THIS SERVER launched for the job - it does not prove a process you separately observe by other means is that one; confirming that remains your own job. Never blocks on the job's own execution.
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": {
"job_id": "<job_id>"
},
"name": "status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | The job id returned by a prior run call. |