Skip to main content
Glama

jobd_status

Read-only

Get full job details—state, exit code, timings, host, dependencies, and termination reason—to check status or debug why a job failed, stalled, or routed. Use wait=true to block until done.

Instructions

The full JobInfo record for one job_id: state, exit_code, timings, host, and the scheduling internals — depends_on + cascade policy (depends_on_any_exit), pending cancel/preempt signal, resolved profile, requires (gpu/tags/idempotent), host pin, fast_path, timeouts, termination_reason. Use for a quick state check AND for debugging why a job routed/failed/stalled. Pass wait=true to block until terminal or wait_timeout_s.

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": "jobd_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
job_idYes
wait_timeout_sNoSeconds, 0 or more. Server clamps to 270.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.58
    • changedInput schema / properties / wait_timeout_s / description
      Previous value: -"Server clamps to 270."New value: +"Seconds, 0 or more. Server clamps to 270."
    • addedInput schema / properties / wait_timeout_s / minimum
      Added value: +0
  2. Changed1 schema field changedv0.5.47
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.5.35
  4. Removedv0.5.34
  5. First observedv0.5.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: wait=true converts the call into a blocking wait for a terminal state. What it omits is what happens on timeout — whether a non-terminal snapshot is returned or an error is raised — which matters for a blocking call.

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

Conciseness4/5

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

Front-loaded with the core identification (full record, single job_id), then purposes, then the wait mechanic. The long mid-sentence field enumeration is dense but it is the only place the return shape is documented since there is no output schema, so those tokens earn their place.

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 field enumeration is essential and is supplied in detail, and the blocking-wait option is explained. Remaining gaps are edge semantics: timeout return behavior and error handling for a nonexistent job_id, which an agent would want before relying on wait=true.

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?

Schema coverage is only 33% (only wait_timeout_s is described), so the description has to carry weight and does: it explains that wait=true blocks until terminal or wait_timeout_s, giving wait a meaning the bare boolean type does not. job_id is self-evident from the required field, though the description never states behavior for an unknown or invalid job_id.

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

Purpose4/5

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

"The full JobInfo record for one job_id" is a specific verb-plus-resource, and the enumeration of returned fields (state, exit_code, depends_on, cascade policy, termination_reason) tells an agent exactly what class of data this is. It distinguishes itself from siblings by implication — one job_id versus the collection-level jobd_list — but never names an alternative, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

"Use for a quick state check AND for debugging why a job routed/failed/stalled" gives two concrete contexts, plus explicit advice on wait=true for blocking until terminal. There is no when-not guidance and no pointer to jobd_logs or jobd_events for the cases this tool does not cover, so an agent must infer the boundary itself.

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