Skip to main content
Glama

print_plate_object

Extract a single object from a multi-object .gcode.3mf file, then upload and start printing it. Supports partial name matching and plate selection.

Instructions

Extract a single object from a multi-object .gcode.3mf and print it.

This is a compound workflow tool that performs the complete pipeline
in one call:

1. **Extract** the requested object's G-code (``extract_plate_object``)
2. **Upload** the extracted G-code to the printer (``upload_file``)
3. **Preflight + Start** the print (``start_print``, which runs its
   own preflight safety check)

Bambu Studio supports multiple plates (plate_1, plate_2, etc.).
Use ``plate_number`` to select which plate to extract and print from.

Object matching is case-insensitive and supports partial names:
``"cap"`` matches ``"TreatHolder - cap.stl"``.

Use ``list_plate_objects`` first if you want to preview what's
available before committing to a print.

:param file_path: Path to the .gcode.3mf file.
:param object_name: Name (or partial name) of the object to print.
:param use_ams: AMS mode — ``"auto"``, ``"true"``, or ``"false"``.
:param ams_mapping: AMS slot mapping (e.g. ``[0]`` for slot 1).
:param bed_leveling: Run bed leveling before print.
:param flow_cali: Run flow calibration before print.
:param vibration_cali: Run vibration calibration before print.
:param bed_type: Bed surface type — ``"auto"``, ``"textured_plate"``,
    ``"cool_plate"``, or ``"engineering_plate"`` (Bambu only).
:param plate_number: Which plate to extract from (1-based, default 1).
:returns: Dict with extraction info and print start status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
use_amsNoauto
bed_typeNoauto
file_pathYes
flow_caliNo
ams_mappingNo
object_nameYes
bed_levelingNo
plate_numberNo
vibration_caliNo
Behavior4/5

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

With no annotations provided, the description bears full responsibility. It details the complete workflow (extract, upload, start print) and notes that start_print runs its own preflight safety check. It also explains object matching behavior. While it could mention potential side effects (e.g., printer state changes), the description is transparent about the pipeline steps.

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 starts with a clear purpose, then uses a numbered list to explain the workflow, followed by parameter details. It is well-structured and each sentence adds value. Although somewhat lengthy, it remains focused and efficient.

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, 2 required, and no output schema, the description explains the workflow, parameter details, and matching logic adequately. It does not cover error handling or preconditions (e.g., printer availability), but for a complex tool with many siblings, it provides sufficient context for agent invocation.

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

Parameters4/5

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

Schema description coverage is 0%, requiring the description to provide parameter details. The description includes a docstring-style list of all parameters with explanations, adding meaning beyond the bare schema (e.g., valid values for use_ams, units for plate_number). This compensates well for the lack of schema descriptions.

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 extracts a single object from a .gcode.3mf file and prints it, with a specific verb-resource combination. It distinguishes itself from siblings by explaining it is a compound workflow that combines extract_plate_object, upload_file, and start_print, which are separate sibling tools.

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 advises using list_plate_objects first to preview available objects, providing clear guidance on when to use this tool vs. an alternative. It also explains case-insensitive and partial name matching. However, it does not explicitly state when not to use this tool or compare to other compound print tools.

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