Skip to main content
Glama

Job List

job_list
Read-only

List every async job in this worker session and diagnose stuck shape optimizations via main-thread queue metrics, showing whether work is slow or not being polled.

Instructions

List every async job this worker session. Returns {count, jobs:[{job_id, kind, status, elapsed_s}]} in submit order, plus main_thread_queue:{queued, ran, failed, drains, pending} — the diagnostic for a shape optimization that looks stuck. Those builds run on the worker's main thread, and that queue is drained once per request: pending high with drains climbing means the work is slow; drains flat means nothing is polling, so nothing is advancing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description goes well beyond them by disclosing the full return shape, ordering (submit order), and how to interpret main_thread_queue fields (pending high + drains climbing = slow; drains flat = nothing polling). That interpretive guidance is exactly the kind of behavior an agent cannot get from structured fields.

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 purpose and return shape, then the diagnostic interpretation. Dense but every sentence carries information; minor cost from an awkward lead phrase ("List every async job this worker session") and a slightly verbose queue explanation.

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 correctly supplies the return payload and its semantics, and the queue diagnostic makes the tool callable for its main use case. It stops short of pointing to job_result/job_status for retrieving a job's output after listing, which an agent will likely need next.

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 coverage is 100% and there is only one optional parameter (workspace), so the schema already documents it fully. The description adds nothing about the workspace parameter — its scope language ("this worker session") arguably sits in mild tension with a workspace override, but the baseline 3 is appropriate.

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?

States a specific verb+resource ("List every async job") scoped to "this worker session", which is concrete and distinct from a status lookup. It does not, however, name or differentiate from the nearby job_status / job_result siblings, so the agent must infer the split.

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?

"The diagnostic for a shape optimization that looks stuck" gives a real usage scenario, which is more than nothing. But there is no explicit rule about when to call this versus job_status or job_result, and the scenario is narrow relative to the tool's general listing capability.

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