Skip to main content
Glama

register_printer

Register a 3D printer with the Kiln fleet. Specify the printer type, host, and API key to enable remote monitoring and job submission via MCP.

Instructions

Register a new printer in the fleet.

Free and Pro each allow 1 printer. Fleet starts at Business (3 printers
included, $15/mo per additional to a cap of 50); Enterprise is uncapped.

Args:
    name: Unique human-readable name (e.g. "voron-350", "bambu-x1c").
    printer_type: Backend type -- "octoprint", "moonraker", "bambu",
        "creality", "elegoo", "prusalink", "duet", or "usb".
        "serial" is accepted as a legacy alias for "usb".
    host: Base URL or IP address of the printer.  For USB printers,
        this is the port path (e.g. "/dev/ttyUSB0", "COM3").
    api_key: API key (required for OctoPrint and Bambu, optional for
        Moonraker/Creality, unused for USB).  For Bambu printers
        this is the LAN Access Code.
    serial: Printer serial number (required for Bambu printers).
    verify_ssl: Whether to verify SSL certificates (default True).
        Set to False for printers using self-signed certificates.
        For Bambu, True maps to TLS pin mode and False maps to
        insecure mode.
    printer_model: Optional safety/profile key (e.g. "k1_max").
    persist: Save the printer to ``~/.kiln/config.yaml`` so future MCP
        sessions load the same printer. Default ``True``.
    verify_connection: For Bambu printers, immediately query AMS status
        after registration and return a proof summary. Default ``True``.
    baudrate: Baud rate for USB printers.  Defaults to
        ``DEFAULT_SERIAL_BAUDRATE``; many Marlin boards are flashed
        for 250000 and will not talk at the default.

Once registered the printer appears in ``fleet_status()`` and can be
targeted by ``submit_job()``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
nameYes
serialNo
api_keyNo
persistNo
baudrateNo
verify_sslNo
printer_typeYes
printer_modelNo
verify_connectionNo
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It details post-registration effects (appears in fleet_status, use with submit_job), default behaviors (persist, verify_ssl, verify_connection), and special cases (Bambu LAN Access Code, legacy alias for serial, baudrate defaults). No contradictions with missing 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 thorough but not overly verbose. It is front-loaded with the main purpose and structured into paragraphs with an Args list. Some information could be streamlined (e.g., tier limits might be secondary), but overall efficiently organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, 3 required, no output schema), the description covers all essential aspects: purpose, usage context, parameter semantics, and post-registration effects. It is complete enough for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage; the description compensates with detailed explanations for all 10 parameters, including allowed values, defaults, and conditional requirements (e.g., serial required for Bambu, api_key usage per type). This adds significant meaning beyond the schema's type/default information.

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 clearly states 'Register a new printer in the fleet' and explains the operational outcome (appears in fleet_status, targetable by submit_job). It is a specific verb-resource pair that distinguishes the tool from siblings like troubleshoot_print_issue or trust_printer.

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 description provides tier-based capacity limits, indicating when registration is possible (e.g., Free/Pro caps at 1 printer). It implies usage context but does not explicitly list alternatives or when not to use this tool relative to siblings like discover_printers or trust_printer.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server