Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

send_to_printer

Upload sliced G-code or .3MF files to a FlashForge Creator 5 over the local network, with optional bed leveling and print start after upload.

Instructions

Upload a sliced file to the Creator 5 over the local network (experimental).

By default the file is only uploaded. Set start_print=True only after the user has confirmed the bed is clear and the right filament is loaded in toolhead 1.

Args: gcode_path: Absolute path to the .gcode or .3mf produced by slice_model. start_print: Start printing straight after upload. level_bed: Run bed levelling before the print starts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gcode_path": "<gcode_path>"
    },
    "name": "send_to_printer"
  }
}

Input Schema

NameRequiredDescriptionDefault
level_bedNo
gcode_pathYes
start_printNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses that the tool is experimental, that it operates over the local network, that upload-only is the default, and that starting a print requires human confirmation of bed and filament state. It stops short of describing failure behavior, whether uploads overwrite existing files on the printer, or what confirmation is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The summary sentence is front-loaded, and the safety-critical caveat about start_print follows immediately rather than being buried. The short Args block is not filler here since the schema has no property descriptions, so every line carries information an agent would otherwise lack.

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?

For a three-parameter mutation tool with no annotations and no output schema, the description covers all parameters plus the main safety hazard, which is what an agent most needs. It leaves open what the tool returns on success and how it behaves when the printer is unreachable or the file is invalid, which a caller might want before committing to a print.

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%, so the description must compensate and largely does: gcode_path is specified as an absolute path to a .gcode or .3mf file produced by slice_model, start_print is explained as print-immediately-after-upload, and level_bed as bed levelling before the print. The one gap is level_bed's default of true, which only appears in the schema, so the interaction between level_bed and start_print is not spelled out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Upload a sliced file'), names the target device ('Creator 5') and transport ('over the local network'), and flags the maturity level ('experimental'). It does not explicitly contrast itself with siblings like slice_model or printer_status, but the reference to 'produced by slice_model' makes the pipeline position clear.

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?

It states a clear default behavior ('By default the file is only uploaded') and an explicit precondition for the riskier mode ('Set start_print=True only after the user has confirmed the bed is clear and the right filament is loaded in toolhead 1'). What is missing is guidance on when the tool should not be used at all, e.g. verifying printer reachability via check_setup or printer_status first.

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