Skip to main content
Glama

List Jobs

list_jobs

Monitor long-running TrueNAS middleware jobs by retrieving job records and filtering by state (RUNNING, SUCCESS, FAILED) to check progress and outcomes.

Instructions

List middleware jobs (long-running operations).

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

Input Schema

NameRequiredDescriptionDefault
stateNoFilter by job state, e.g. RUNNING, SUCCESS, FAILED (optional).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it does not state read-only behavior, pagination, ordering, whether completed jobs are included, or any auth/rate-limit considerations. The phrase 'long-running operations' adds context, but not enough operational transparency.

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?

The description is a single front-loaded sentence with no wasted words. The parenthetical adds useful clarification without disrupting conciseness.

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

Completeness3/5

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

For a simple list tool with a fully documented parameter and an output schema, the description is minimally adequate. However, the absence of annotations and the lack of usage and behavioral context leave clear gaps for an agent deciding how and when to invoke it.

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?

The single optional state parameter is fully documented in the schema, including examples such as RUNNING, SUCCESS, and FAILED. The description adds no parameter semantics beyond what the schema already provides, which is the baseline case when schema coverage is 100%.

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 description names a specific verb and resource, 'List middleware jobs', and the parenthetical clarifies that these are long-running operations. It does not, however, distinguish this tool from sibling list tools or status-oriented tools such as get_scrub_status.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use list_jobs versus alternatives, nor any exclusions or prerequisites. The only usage signal is the implied action of listing jobs.

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