Skip to main content
Glama
Sign In

SimplyPrint: 3D Print Farm Management

by io.simplyprint
OverviewDiscussionsAdmin

send_gcode

Destructive

Send G-code commands to a printer

Input Schema

NameRequiredDescriptionDefault
gcodeNoArray of G-code commands to send. Either gcode, macro, macros, or snippet_id is required.
macroNoPredefined macro name to execute. Either gcode, macro, macros, or snippet_id is required.
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.
macro_contextNoOptional context data for macro execution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / gcode / description
      Previous value: -"Array of G-code commands to send. Either gcode, macro, or snippet_id is required."New value: +"Array of G-code commands to send. Either gcode, macro, macros, or snippet_id is required."
    • changedInput schema / properties / macro / description
      Previous value: -"Predefined macro name to execute. Either gcode, macro, or snippet_id is required."New value: +"Predefined macro name to execute. Either gcode, macro, macros, or snippet_id is required."
    • 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. Changed1 schema field changed
    • changedInput schema / properties / macro / enum
      Previous value: -[
-  "is_start",
-  "is_end",
-  "is_cancel",
-  "is_pause",
-  "is_resume",
-  "move_axis",
-  "change_print_speed",
-  "change_flow_rate",
-  "is_home",
-  "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"
-]New value: +[
+  "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"
+]
  3. 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 readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is carried by structured data. The description adds nothing beyond that — it omits execution semantics such as whether commands run immediately or queue, what happens with multiple printer IDs, ordering guarantees across the gcode array, and failure behavior for invalid lines. No contradiction with annotations exists, since sending G-code is genuinely a mutating, destructive operation.

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 zero redundant wording. It is efficient rather than padded, though the terseness trades off against needed detail elsewhere.

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

Completeness2/5

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

For a destructive, open-world tool with six parameters, multiple mutually-exclusive input modes, a 200-item command cap, and multi-printer targeting, the description does almost none of the work. It provides no operational context about execution, safety, or result behavior, and there is no output schema to compensate.

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%, so every parameter including the mutually-exclusive gcode/macro/macros/snippet_id set is already documented. The description contributes no additional parameter meaning, but per the coverage rule the schema carrying the load justifies a baseline 3.

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 states a specific verb and resource ('Send G-code commands to a printer'), which is unambiguous on its face. It does not, however, distinguish this raw-command tool from higher-level siblings such as move_printer_axis, home_printer, or set_printer_temperatures, leaving the agent to infer the boundary.

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 guidance, no exclusion of alternatives, and no prerequisites (e.g., printer must be idle, must be in the right state). Usage is only implied by 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