Skip to main content
Glama

job_list

Read-onlyIdempotent

List background shells in a workspace with their current state and exit code, so you can monitor running jobs and diagnose failures.

Instructions

List this workspace's background shells with state and exit code.

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
fleetNoFleet name. Omit to use the default.
contextNoContext name. Omit to use the default.
workspaceNoWorkspace id. Omit to use this session's workspace on the fleet.

Output Schema

NameRequiredDescriptionDefault
whereYes
shellsYes
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is clear without prose. The description adds only that state and exit code are reported; it says nothing about whether finished shells are retained, ordering, result limits, or pagination.

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?

One short sentence with the scope and returned fields front-loaded and no filler. Nothing is wasted, though it is terse enough that a clarifying clause about scope or alternatives could have been added at little cost.

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?

Output schema exists and annotations cover safety, so the description need not explain return values or side effects. The one residual gap is that 'this workspace's' sits slightly at odds with the fleet/context/workspace parameters that let the caller target a different workspace.

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 100%, so the fleet, context, and workspace parameters are fully documented in the schema and a baseline of 3 applies. The description's 'this workspace's' phrasing weakly signals the default workspace scoping that the workspace parameter overrides, so it edges slightly above baseline.

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?

Specific verb (List) plus resource (this workspace's background shells) and the fields returned (state, exit code). An agent can distinguish it from output-reading siblings like bash_output or read_output, though no sibling is named explicitly for contrast.

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 only implied: an agent infers it should call this to discover background shells before reading output or killing one. There is no explicit when-to-use or when-not-to-use statement, and no sibling such as bash_output, read_output, or kill_shell is referenced.

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