Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

queue_summary

Read-only

Summarizes the 3D print queue: job counts by status, next job, recent jobs, stalled or stopped alerts, waiting reasons, and printers needing plate clearing.

Instructions

Get an overview of the print job queue.

Returns counts by status, next job to execute, recent jobs,
``watch_alerts``: watched prints that have stalled or stopped answering
and need a person (they stay active until the printer ends them or
someone cancels), ``waiting``: every queued job with why it has not
started and a sentence to show (see ``job_status``), and
``plates_to_clear``: the printers whose last print is still on the plate
and holding the line.  A finished part is never printed onto: the queue
waits for the person to clear the plate and say so, then starts the next
job by itself.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description explains meaningful queue behavior: watch_alerts stay active until the printer ends them or someone cancels, waiting jobs include why they have not started, and plates_to_clear block the queue until a person clears the plate. It also states that the queue automatically starts the next job after the plate is cleared, which is valuable operational context not captured by the read-only annotations.

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?

The description is front-loaded with the core purpose and then explains return sections in a logical order. It is somewhat longer than necessary, with unusual backtick formatting and line breaks, but most sentences add useful operational detail rather than repeating the name or annotations.

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 carries the burden of explaining return values, and it does so for the main sections: counts by status, next job, recent jobs, watch_alerts, waiting, and plates_to_clear. It leaves some ambiguity about the exact shape of "counts by status" and "recent jobs," but overall it is complete enough for an agent to understand what the tool provides.

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?

The tool takes zero parameters, so there is no parameter semantics to document. The baseline for a zero-parameter tool is 4, and the description appropriately avoids inventing parameter details.

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 opens with a specific verb and resource: "Get an overview of the print job queue." It then enumerates the returned sections (counts by status, next job, recent jobs, watch_alerts, waiting, plates_to_clear), which distinguishes it from sibling tools like job_status and job_history.

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 implied rather than explicitly stated: the tool is for an overview, and the description points to job_status for per-job waiting reasons. However, it does not say when to choose queue_summary over job_status, job_history, or printer_status, nor does it state any exclusions.

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