Skip to main content
Glama

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

NameRequiredDescriptionDefault
job_idYesThe job id returned by a prior run call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does substantial work: it discloses non-blocking behavior, conditional return fields ('as applicable'), and detailed semantics of pid/birth_identity including pending/captured/unavailable states and platform-specific identity kinds. It stops short of stating failure behavior for an unknown or already-purged job_id, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, which is good, but the remainder is a long, dense run-on devoted largely to birth_identity provenance. That detail is genuinely non-obvious and not covered by schema or annotations, so it earns some space, yet the wording is heavier than needed and could be tightened considerably.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description effectively doubles as a return-value contract by naming state, timestamps, exit_code/signal/diagnostic, pid, and birth_identity. It is complete enough for correct invocation, missing only error/unknown-job handling to be fully self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema (job_id with minLength and a description pointing to a prior run call), and the description reinforces that provenance by tying the job to 'started by run.' Little extra meaning is needed for a one-parameter tool, though it could note what happens with a stale or unknown id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the current lifecycle status of a background job started by run') and enumerates the exact state values (starting/running/exited/killed/failed) plus timestamps and exit_code/signal/diagnostic. This clearly separates it from siblings like output, tail, and follow, which stream content rather than report lifecycle state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the reference to a job 'started by run' and the note that it 'Never blocks on the job's own execution,' which signals a polling use case. However, it never explicitly contrasts with siblings (e.g., use output/tail to read logs, use list to enumerate jobs), so the agent must infer when this is the right call versus an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools