Skip to main content
Glama

pause_print

Pause a 3D print job while maintaining nozzle and bed temperatures to prevent cooling and failed recovery.

Instructions

Pause the currently running print job.

Pausing lifts the nozzle and parks the head.

Heater behaviour during pause varies by firmware:

  - Bambu A1 / A1 mini: the firmware drops the **hotend** target
    ~3-5 minutes into a pause regardless of slicer settings (bed
    target survives).  An untreated 25-min pause cools the nozzle
    from 220°C to ~90°C, which means the resume can't extrude
    until you re-heat — and bed adhesion can fail in the meantime.
  - Bambu X1/P1 series: typically holds both targets, but a long
    idle can still trigger cooldown.
  - OctoPrint / Moonraker / Klipper: depends on firmware config;
    most hold targets across pause.

To fight this, ``pause_print`` spawns a best-effort daemon thread
that re-asserts the pre-pause hotend + bed targets every 2 minutes
until the printer leaves the PAUSED state (resume, cancel, error,
or manual button press).  This is enabled by default.

Args:
    keep_temps: When ``True`` (default), capture the pre-pause tool
        and bed targets and re-assert them every ~2 minutes via a
        background daemon thread.  Set ``False`` to skip the
        keep-alive (legacy behaviour — printer may cool during long
        pauses).  The keep-alive thread is idempotent: repeat
        pause/resume cycles do not compound threads.

Use ``resume_print()`` to continue from where the print left off.
The keep-alive thread is automatically stopped on resume or cancel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keep_tempsNo
Behavior5/5

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

With no annotations, the description fully discloses tool behavior: nozzle and head movement, firmware-specific heater behavior, daemon thread for keep-alive, parameter effect, and thread idempotency. No contradictions.

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 longer but well-structured: purpose, firmware details, solution, parameter, follow-up. Every sentence adds value; could be slightly tighter but appropriate for complexity.

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 no output schema and one parameter, the description covers all aspects: what happens during pause, firmware differences, temperature management, parameter details, and how to resume. Complete.

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?

The single parameter `keep_temps` is thoroughly explained: default behavior, what it does (re-asserts targets every 2 minutes), and idempotency. Schema coverage is 0%, but the description compensates fully.

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 the tool's function: 'Pause the currently running print job.' It details what happens (lifts nozzle, parks head) and distinguishes from siblings like cancel_print by mentioning resume_print() as a follow-up.

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 implies when to use (pause a running print) and provides guidance on heater behavior variations by firmware. It does not explicitly state when not to use, but the context is clear.

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