Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

register_printer

Register a printer to your fleet for centralized management and job submission. Supports multiple printer backends such as OctoPrint, Moonraker, and Bambu.

Instructions

Register a new printer in the fleet.

Free tier allows up to 2 printers with independent control.
Pro tier unlocks unlimited printers with fleet orchestration.

Args:
    name: Unique human-readable name (e.g. "voron-350", "bambu-x1c").
    printer_type: Backend type -- "octoprint", "moonraker", "bambu",
        "creality", "elegoo", "prusalink", or "serial".
    host: Base URL or IP address of the printer.  For serial 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 serial).  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``.

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
verify_sslNo
printer_typeYes
printer_modelNo
verify_connectionNo

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses parameter behaviors (e.g., persist saves to config, verify_ssl nuances for Bambu) and notes registration effect on fleet_status. However, it does not mention potential side effects like overwriting existing registrations or authentication requirements beyond the api_key parameter.

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?

Description is well-structured with tier info first, then a detailed Args list. It is efficient but slightly verbose for a tool with many parameters. Every sentence adds value, but could be trimmed without losing clarity.

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?

Given 9 parameters, no output schema, and no annotations, the description covers all parameters, side effects, and tier restrictions. Missing are error conditions (e.g., duplicate name) and required permissions. For a registration tool, it is fairly complete but not exhaustive.

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 coverage is 0%, but the description provides extensive detail for all 9 parameters, including printer_type backend list, host format for serial, api_key per printer type, verify_ssl mapping for Bambu, and verify_connection purpose. This adds significant meaning beyond the bare schema.

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?

Description clearly states 'Register a new printer in the fleet' – a specific verb and resource. It also explains post-registration behavior (appears in fleet_status, targetable by submit_job), distinguishing it from sibling tools like trust_printer or discover_printers.

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?

Description provides context on free vs. pro tier limits, implying when registration is allowed. However, it does not explicitly contrast with alternative tools or state when not to use (e.g., if printer already registered, update via other means). The context is clear but lacks exclusions.

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