Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

discover_printers

Read-only

Scan your local network to find OctoPrint, Moonraker, Bambu Lab, Elegoo, and Prusa 3D printers. Returns host, port, type, and the details needed to register each one.

Instructions

Scan the local network for 3D printers.

        Uses mDNS/Bonjour and HTTP subnet probing to find OctoPrint,
        Moonraker/Creality, Bambu Lab, Elegoo, and Prusa printers on
        the local network.

        Args:
            timeout: Maximum scan duration in seconds (default 5).

        Returns a list of discovered printers with host, port, type, and
        whether the API is reachable.  Each one also carries
        ``address`` -- pass it as ``register_printer``'s ``host``; it
        keeps the port the printer answered on -- and ``to_connect``:
        what the person still has to supply and where they find it
        (``still_needed``), and anything to switch on in the printer
        first (``first``).  Ask for exactly those, in plain words, then
        add the printer with ``register_printer``.  ``suggested_name``
        is a name for it with no address or serial in it; propose that
        name, and use the person's own name when they give one.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNoMaximum scan duration in seconds (default 5). Default: 5.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / timeout / description
      Previous value: -"Default: 5.0."New value: +"Maximum scan duration in seconds (default 5). Default: 5.0."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / timeout / default
      Removed value: -5
    • addedInput schema / properties / timeout / description
      Added value: +"Default: 5.0."
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds real behavioral detail beyond that by naming the discovery mechanisms (mDNS/Bonjour plus HTTP subnet probing), listing supported ecosystems, and explaining that returned records encode the port the printer answered on and the remaining setup steps. With no output schema, this return-shape disclosure is doing important work. It omits any mention of failure modes such as firewalls, empty results, or subnet scope limits, so it is not fully transparent.

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 purpose is front-loaded in the first sentence, and the remainder is organized into protocol coverage, arguments, and return-field guidance. It is somewhat verbose, and the Args section duplicates a schema field that is already 100% documented, which is wasted space. Otherwise every sentence carries actionable information for the follow-up flow.

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?

There is no output schema, so the description must describe the return value, and it does so thoroughly: host, port, type, API reachability, the ``address`` field to reuse, the ``to_connect`` breakdown, and a ``suggested_name``. For a zero-required-parameter discovery tool with annotations covering safety, an agent has everything needed to call it and act on the result.

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?

Only one parameter exists and schema coverage is 100%, with the schema already stating "Maximum scan duration in seconds (default 5)"; the Args block in the description merely restates it. Baseline 3 applies because the schema carries the parameter meaning and the description adds no syntax, unit, or trade-off nuance beyond it.

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?

"Scan the local network for 3D printers" gives a specific verb plus resource, and the second paragraph names the discovery protocols and the exact printer brands covered, so the agent knows precisely what class of device is found. It is clearly distinct from siblings such as register_printer, list_trusted_printers, or printer_status, which assume a known printer rather than searching for one.

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 establishes a workflow: run this scan, then feed the returned ``address`` into ``register_printer``'s ``host``, and ask the person only for what ``to_connect.still_needed`` lists. That is explicit context for when this tool belongs in a sequence. It stops short of stating exclusions (e.g., when to use a known-printer tool instead of scanning, or what to do if nothing is found), which is why it is a 4 rather than 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