Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_snapshots

Read-only

Retrieve snapshot metadata to review print history and correlate captures with outcomes. Filter by printer, job, phase, or limit.

Instructions

List persisted snapshots from the database.

Returns metadata for snapshots captured during print monitoring,
timelapses, or manual captures.  Use this to review print history
visually or correlate snapshots with print outcomes.

Args:
    printer_name: Filter by printer name.
    job_id: Filter by job or timelapse ID.
    phase: Filter by capture phase as the monitor records it:
        ``"first_layers"``, ``"mid_print"``, ``"final_layers"`` or
        ``"unknown"``.
    limit: Maximum records to return (default 20).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records to return (default 20). Default: 20.
phaseNoFilter by capture phase as the monitor records it: ``"first_layers"``, ``"mid_print"``, ``"final_layers"`` or ``"unknown"``.
job_idNoFilter by job or timelapse ID.
printer_nameNoFilter by printer name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • addedInput schema / properties / job_id / description
      Added value: +"Filter by job or timelapse ID."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 20."New value: +"Maximum records to return (default 20). Default: 20."
    • addedInput schema / properties / phase / description
      Added value: +"Filter by capture phase as the monitor records it: ``\"first_layers\"``, ``\"mid_print\"``, ``\"final_layers\"`` or ``\"unknown\"``."
    • addedInput schema / properties / printer_name / description
      Added value: +"Filter by printer name."
  2. Changed5 schema fields changedv1.5.0
    • removedInput schema / properties / job_id / default
      Removed value: -null
    • removedInput schema / properties / limit / default
      Removed value: -20
    • addedInput schema / properties / limit / description
      Added value: +"Default: 20."
    • removedInput schema / properties / phase / default
      Removed value: -null
    • removedInput schema / properties / printer_name / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description's help. The description does add one useful behavioral fact beyond annotations — that it returns metadata rather than image data — but says nothing about result ordering, pagination behavior beyond the limit cap, or empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prose portion is well front-loaded and efficient, leading with purpose then use case. The four-entry Args block, however, is a near-verbatim duplicate of schema fields that the agent already receives, consuming roughly half the description without earning its place.

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 read-only list tool with four optional filters and no output schema, the description covers purpose, source, use case, and the fact that metadata (not images) is returned. The remaining gap — ordering and total-count/pagination semantics, which matter without an output schema — is modest.

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 100%, and the Args block restates the four parameter descriptions almost verbatim from the schema, including the phase value list. It adds essentially no meaning beyond what the structured schema already provides, so the baseline of 3 applies.

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 and resource ("List persisted snapshots from the database") and narrows the content to snapshot metadata captured during print monitoring, timelapses, or manual captures. An agent can distinguish it from analyze_print_snapshot or printer_snapshot on the basis of "metadata listing" vs. capture/analysis, though no sibling is named explicitly.

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?

"Use this to review print history visually or correlate snapshots with print outcomes" gives real usage context, so the agent knows the intent behind calling it. However, there are no exclusions or named alternatives — nothing says when to prefer analyze_print_snapshot for a specific image, or that other tools handle live capture — so the routing decision is left to inference.

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