Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

validate_print_quality

Assesses completed 3D print quality by capturing a webcam snapshot and reviewing job records, then returns detected issues and recommendations.

Instructions

Validate print quality after a completed print job.

        Captures a webcam snapshot (if available), examines the job record and
        events, and produces a quality assessment with recommendations.

        Args:
            job_id: The completed job's ID.  If omitted, uses the most recent
                completed job.
            printer_name: Target printer name (omit for default printer).
            save_snapshot: Optional file path to save the post-print snapshot.

        Returns a quality report with snapshot data, job metrics, and any
        detected issues.

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

Input Schema

NameRequiredDescriptionDefault
job_idNoThe completed job's ID. If omitted, uses the most recent completed job.
printer_nameNoTarget printer name (omit for default printer).
save_snapshotNoOptional file path to save the post-print snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / job_id / description
      Added value: +"The completed job's ID.  If omitted, uses the most recent completed job."
    • addedInput schema / properties / printer_name / description
      Added value: +"Target printer name (omit for default printer)."
    • addedInput schema / properties / save_snapshot / description
      Added value: +"Optional file path to save the post-print snapshot."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / job_id / default
      Removed value: -null
    • removedInput schema / properties / printer_name / default
      Removed value: -null
    • removedInput schema / properties / save_snapshot / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool captures a webcam snapshot if available, examines the job record and events, and can optionally save the snapshot to a file path. This is useful behavioral context for a tool marked non-read-only, though it does not discuss permissions, latency, or side effects of snapshot capture in detail.

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 well organized and front-loads the main purpose before listing arguments and return behavior. It is appropriately sized, though it duplicates some parameter text already present in the schema.

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 appropriately states that the tool returns a quality report with snapshot data, job metrics, and detected issues. Combined with the parameter and behavioral details, it provides enough context for an agent to invoke the tool correctly, despite minor gaps around side effects and alternatives.

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%, so the schema already documents all three parameters. The description repeats the same parameter meanings without adding significant new syntax, constraints, or edge-case guidance beyond what the schema already provides.

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 gives a specific verb and resource: validate print quality after a completed print job, using a webcam snapshot plus job records and events. It is clear about what the tool does, but it does not explicitly distinguish itself from close siblings such as analyze_print_snapshot or analyze_print_failure.

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?

It states the key precondition that the job must be completed, and that job_id defaults to the most recent completed job. However, it gives no explicit when-not-to-use guidance and does not point to alternatives for related tasks like failure analysis or snapshot-only analysis.

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