Skip to main content
Glama
Sign In

SimplyPrint: 3D Print Farm Management

by io.simplyprint
OverviewDiscussionsAdmin

set_printer_motors

Enable or disable the printer stepper motors

Input Schema

NameRequiredDescriptionDefault
macrosNoPredefined macro names, sent as one G-code block in this order. Either gcode, macro, macros, or snippet_id is required.
enabledYesMotor state: "on" to enable motors (lock axes), "off" to disable (allow manual movement)
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

C2.9/5.0
Behavior2/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, so the description could have added what those hints can't say — e.g., that disabling motors frees axes for manual movement and can disrupt an in-progress job. Instead it only restates the action, adding no context beyond the structured fields.

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 no wasted words. It is almost too terse, but brevity itself is not penalized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no output schema, the description should at least explain how the optional macros/snippet_id parameters interact with the motor action (the schema text also references gcode and macro parameters that don't appear in the schema, which is confusing). Annotations plus schema carry most of the load, so the definition is barely adequate as-is.

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% and the every parameter carries its own description (including the on/off semantics). The description adds nothing further, which meets the baseline 3 for a fully documented schema.

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?

Description states a specific verb pair (enable/disable) and resource (printer stepper motors), which is unambiguous and distinguishable from siblings like move_printer_axis or home_printer. It stops short of explicitly contrasting with those siblings, so it lands at 4 rather than 5.

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?

No guidance on when to use this versus send_gcode, home_printer, or move_printer_axis, and no mention of preconditions (e.g., not during an active print). The agent must infer usage entirely from the tool name.

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