Skip to main content
Glama
musharna

jobd

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jobd_list

List jobs on the broker with per-state counts, filterable by state or project. Shows compact summaries of job id, state, host, and times. Use to find running or queued jobs or locate a job ID.

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. Addedv0.5.36
  2. Removedv0.5.35
  3. 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."
  4. 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)."
  5. First observedv0.5.5

TDQS

A4.7/5.0
Behavior4/5

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

Discloses default behavior, filtering, row fields, limit clamping, and truncated field. Without annotations, it covers read-only nature and pagination, but lacks mention of authentication or rate limits.

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?

Four sentences, front-loaded with purpose, no redundancy. Every sentence adds value: purpose, filtering options, row contents, and guidance to sibling tool.

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?

Explains row fields and counts, mentions truncated field. No output schema, but adequately describes return structure. Missing explicit sort order (newest first only in schema description), but overall sufficient.

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

Parameters5/5

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

Adds significant meaning beyond schema: explains default state set, provides example filter values, clarifies limit behavior with truncated reporting, and describes project restriction context.

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 clearly states it lists jobs with per-state counts, uses specific verb 'List', and explicitly distinguishes from sibling tool jobd_status for full records.

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

Usage Guidelines5/5

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

Provides explicit use cases: 'what is running / queued right now?' and locating job IDs. States defaults and filtering options, and directs to jobd_status for full details, effectively guiding when to use alternatives.

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