Skip to main content
Glama
musharna

jobd

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jobd_list

List jobs on the broker with per-state counts. Filter by state or project to locate running, queued, or past runs and find lost job ids.

Instructions

List jobs on the broker with per-state counts. Defaults to the active set (queued/assigned/running); filter by state (e.g. ['failed']) or project to find past runs. Each row is a compact summary: job_id, project, state, host, exit_code, queued_at, started_at — call jobd_status for a job's full record. Use to answer 'what is running / queued right now?' or to locate a job id you've lost.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax jobs returned (newest first; clamped to [1,200]). `counts` still covers every job matching the filters; a `truncated` field reports how many were cut.
stateNoStates to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Omit for the active set (queued/assigned/running); pass [] for all states.
projectNoRestrict to one project's jobs (the --project value used at submit).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.47
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / state / items / enum
      Added value: +[
+  "queued",
+  "assigned",
+  "running",
+  "completed",
+  "failed",
+  "cancelled",
+  "preempted",
+  "orphaned",
+  "scheduling_timeout"
+]
  2. Addedv0.5.36
  3. Removedv0.5.35
  4. Changed2 schema fields changedv0.5.12
    • changedInput schema / properties / limit / description
      Previous value: -"Advisory cap on returned jobs (the broker currently returns its default window)."New value: +"Max jobs returned (newest first; clamped to [1,200]). `counts` still covers every job matching the filters; a `truncated` field reports how many were cut."
    • changedInput schema / properties / state / description
      Previous value: -"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Currently only the first is forwarded to the broker (single state_filter)."New value: +"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Omit for the active set (queued/assigned/running); pass [] for all states."
  5. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Advisory cap on returned jobs (the broker currently returns its default window)."
    • addedInput schema / properties / project / description
      Added value: +"Restrict to one project's jobs (the --project value used at submit)."
    • changedInput schema / properties / state / description
      Previous value: -"States to include. Currently only the first is forwarded to the broker (single state_filter)."New value: +"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Currently only the first is forwarded to the broker (single state_filter)."
  6. First observedv0.5.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool defaults to the active set, returns per-state counts, and emits compact summary rows with specified fields. It also clarifies that jobd_status is needed for full records. It doesn't explicitly state that the operation is read-only or side-effect-free, but the verb 'list' implies it, and the behavior described is accurate and useful.

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

Conciseness5/5

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

Three sentences, each earning its place: purpose plus default scope, filtering guidance, and output format with a pointer to jobd_status. The most important operational details are front-loaded, with no filler or repetition of schema content.

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

Completeness5/5

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

No output schema exists, so the description compensates by enumerating the row fields and indicating that counts accompany the list. It also explains defaults, filter options, and how to get full records. This is complete for a list-style tool of moderate complexity, and the schema handles the remaining input details.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds a little usage context ('filter by state (e.g. ["failed"]) or project to find past runs') but does not materially extend what the schema already documents. It earns the baseline but no more.

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?

The description opens with a specific verb and resource: 'List jobs on the broker with per-state counts.' It clearly distinguishes itself from sibling jobd_status by stating that each row is a compact summary and that jobd_status provides the full record. An agent can immediately tell what this tool does and how it differs from related tools.

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?

It states when to use the tool: answer 'what is running / queued right now?' or locate a lost job id, and it explains the default active set and how to filter by state or project for past runs. It doesn't explicitly say 'use this instead of X' beyond pointing to jobd_status for full records, but the use case is clearly scoped.

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