Skip to main content
Glama
Sign In

SimplyPrint: 3D Print Farm Management

by io.simplyprint
OverviewDiscussionsAdmin

home_printer

Home the printer axes (move to origin position)

Input Schema

NameRequiredDescriptionDefault
axesNoAxes to home, space-separated. Examples: "X Y Z" (all), "X Y" (XY only), "Z" (Z only)X Y Z
macrosNoPredefined macro names, sent as one G-code block in this order. Either gcode, macro, macros, or snippet_id is required.
printer_idYesThe printer IDs (comma-separated for multiple)
snippet_idNoID of a gcode snippet to send. Either gcode, macro, macros, or snippet_id is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / macros
      Added value: +{
+  "description": "Predefined macro names, sent as one G-code block in this order. Either gcode, macro, macros, or snippet_id is required.",
+  "items": {
+    "enum": [
+      "is_start",
+      "is_end",
+      "is_cancel",
+      "is_pause",
+      "is_resume",
+      "move_axis",
+      "change_print_speed",
+      "change_flow_rate",
+      "is_home",
+      "set_tool_temperature",
+      "set_bed_temperature",
+      "set_chamber_temperature",
+      "motors_onoff",
+      "fans_onoff",
+      "baby_stepping",
+      "z_offset_cal_start",
+      "z_offset_cal_nudge",
+      "z_offset_cal_save",
+      "is_autoprint_clear",
+      "is_autoprint_on_end"
+    ],
+    "type": "string"
+  },
+  "maxItems": 5,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / snippet_id / description
      Previous value: -"ID of a gcode snippet to send. Either gcode, macro, or snippet_id is required."New value: +"ID of a gcode snippet to send. Either gcode, macro, macros, or snippet_id is required."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the useful clarification that homing means moving to the origin, but omits operational consequences: whether the current print is interrupted, whether the call blocks until the move completes, and what happens on a failed home.

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?

A single front-loaded sentence with the core action first and the parenthetical clarification second; zero waste. It is arguably too terse given the tool's side effects, but nothing is redundant.

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?

The tool is simple (4 params, one required, no nested objects, no output schema) and the schema carries detailed parameter documentation, so the description does not need to repeat it. What is missing is behavioral context around a physical motion command – interruption of active jobs and blocking semantics – which keeps it below a 5.

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?

Schema description coverage is 100% – axes format, macro list semantics, and the 'either gcode, macro, macros, or snippet_id' requirement are all documented in the schema. The description adds nothing about parameters, so the baseline of 3 applies.

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?

States a specific verb and resource ('Home the printer axes') and clarifies the operation with '(move to origin position)'. It is distinguishable from move_printer_axis by the word 'home', though the description never names that sibling to sharpen the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no mention of the closest alternative (move_printer_axis). An agent must infer that homing is the right choice versus an incremental move, and gets no warning about homing while a print is running.

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

All SimplyPrint: 3D Print Farm Management toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources