Skip to main content
Glama

queue

Manage render jobs by listing, pausing, resuming, clearing, prioritizing, or moving waiting tasks to the front so ComfyUI renders run in the intended order.

Instructions

The render queue. action: list (default) | pause (nothing new starts; the current render finishes) | resume | clear (cancels waiting jobs; priority="batch" clears only batch jobs) | front (move waiting job id first) | priority (set job id to priority "user" or "batch").

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

Input Schema

NameRequiredDescriptionDefault
idNo
actionNolist
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: pause lets the in-flight render finish, clear only affects waiting jobs, and priority scoping changes what clear touches. However, it says nothing about whether cancelled jobs are recoverable, whether these actions require ownership or permissions, or what a list returns. Note the mild tension with destructiveHint=false, since clear discards queued work — cancellation appears reversible by re-queuing, so this is not a hard contradiction.

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?

A single front-loaded sentence naming the resource, followed by a pipe-delimited action table where every segment adds a distinct constraint or behavior. No filler and no repetition of the tool name.

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?

For a six-action mutation tool with no output schema and bare annotations, the description covers the operational semantics of every action, which is the critical gap. It stops short of explaining what a list returns or the preconditions for supplying id, leaving minor questions for the agent.

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 0% and no enums are declared, so the description must carry the parameter burden. It largely does: action values are all enumerated, id is tied to front and priority, and priority accepts "user" or "batch". It never states that id is required for front/priority or that priority only matters alongside the clear/priority actions, so some inference remains.

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 identifies the resource ("The render queue") and enumerates the concrete operations available (list, pause, resume, clear, front, priority) with a default named. An agent can tell what the tool manipulates and which action it would invoke, though it does not differentiate itself from siblings like cancel or diagnose_job.

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?

Each action carries the context needed to choose it: pause is for stopping new work while letting the current render finish, clear is for discarding waiting jobs with an optional batch-only scope, front and priority target a specific job. There are no explicit when-not conditions or named alternatives, which keeps it short of a 5.

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