Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_printer_variants

Read-only

Lists the verified hardware variants available for a printer, showing each modified configuration's limits next to the as-shipped settings so you can compare changes before selecting one.

Instructions

Show the curated hardware variants available for a printer.

        A curated profile describes a printer AS SHIPPED.  When Kiln has
        verified a documented hardware change — an Ender 3 whose PTFE-lined
        hotend has been replaced with an E3D Revo CR, say — that
        configuration is curated as a VARIANT, with its own limits, its
        manufacturer source, and the preconditions that make it true.

        Returns the as-shipped limits alongside each variant's, so you can
        see what selecting one would change before selecting it.  An empty
        ``variants`` map is the honest answer for a machine Kiln has not
        verified a modified configuration for.

        Args:
            printer_model: Printer identifier (e.g. ``"ender3"``).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "printer_model": "<printer_model>"
    },
    "name": "list_printer_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_modelYesPrinter identifier (e.g. ``"ender3"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_model / description
      Added value: +"Printer identifier (e.g. ``\"ender3\"``)."
  2. Addedv1.3.1

TDQS

A3.8/5.0
Behavior4/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. The description adds real substance beyond that: it discloses the return shape (as-shipped limits alongside each variant's limits) and the meaning of an empty variants map, which the agent could not infer from annotations. Return formatting/pagination detail is absent but minor for a small curated list.

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 core conceptual explanation is front-loaded and earns its place, but the trailing Args section is pure duplication of the input schema, and the middle paragraph is wordier than needed for the amount of information conveyed. Trimming the Args block would leave a tighter definition.

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 correctly carries the burden of explaining what comes back (as-shipped limits plus per-variant limits) and how to read an empty result. Combined with annotations covering safety and a fully documented single parameter, an agent has enough to call this correctly; only unknown-model error behavior is unstated.

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 coverage is 100% for the single parameter, and the description's Args block merely repeats the schema's identical text ("Printer identifier (e.g. \"ender3\")"). It adds no new meaning about the identifier format, resolution rules, or what happens with an unknown model, so baseline 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 ("Show the curated hardware variants available for a printer") and carefully defines what a variant is versus an as-shipped profile, which is genuinely differentiating context. It stops short of naming the sibling tool select_printer_variant, only alluding to it via "before selecting it," so it is clear but not fully sibling-differentiated.

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?

The line "so you can see what selecting one would change before selecting it" clearly frames the use case as a pre-selection inspection step, and the note about an empty variants map being the honest answer tells the agent how to interpret a negative result. There is no explicit "do not use this when..." or named alternative, which keeps it from a 5.

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