Skip to main content
Glama

SimplyPrint: 3D Print Farm Management

by io.simplyprint

set_printer_temperatures

Set target temperatures (nozzle, bed and/or chamber) on one or more printers - works while idle and mid-print. Values above the printer model maximum are clamped; 0 turns a heater off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bedNoTarget heated bed temperature in degrees Celsius. 0 turns the bed heater off. Values above the printer model maximum are clamped. At least one of tool, bed or chamber is required.
toolNoTarget nozzle temperature in degrees Celsius. 0 turns the hotend off. Values above the printer model maximum are clamped. At least one of tool, bed or chamber is required.
chamberNoTarget chamber temperature in degrees Celsius. 0 turns the chamber heater off. Skipped for printers without an actively heated chamber. At least one of tool, bed or chamber is required.
printer_idYesThe printer IDs (comma-separated for multiple)
tool_indexNoZero-based tool index for multi-tool printers. Requires tool to be set. Defaults to 0.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only indicate readOnlyHint=false, so the description carries the disclosure burden. It adds important behavioral traits: values are clamped to printer maxima, 0 turns heaters off, and operation is valid mid-print. This goes beyond basic mutation semantics.

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?

A single sentence, front-loaded with the action and resource, followed by concise behavioral conditions. Every phrase earns its place with no redundancy.

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?

Covers core behavior, timing, and limits. The schema details parameter requirements like at least one of tool/bed/chamber and comma-separated printer IDs. Without an output schema, this is sufficient for selection and invocation, though slightly lighter on return behavior.

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 the schema already documents each parameter. The description reinforces general clamping and zero-off behavior, but adds no new parameter-level information beyond what the schema provides.

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 opens with 'Set target temperatures' and specifies the exact components (nozzle, bed, chamber) and scope (one or more printers). This clearly identifies the tool's function and differentiates it from sibling setters like set_printer_fans and set_printer_motors.

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 notes 'works while idle and mid-print,' providing clear context when the tool is applicable. It does not explicitly name alternatives or exclusion scenarios, but the context is sufficient for an agent to know when to use it.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation3/5

Most tools are clearly separated by resource and action, but several overlapping queue-related tools exist—get_next_queue_item vs get_next_queue_items_for_printers, list_queue vs list_pending_queue_items, and inspect_printer_queue—which could cause misselection. list_custom_fields vs list_custom_fields_for and add_to_queue vs create_print_job add further ambiguity.

Naming Consistency4/5

Names overwhelmingly follow a verb_noun snake_case pattern with consistent resource nouns like print_job, queue_item, folder, and filament. Minor inconsistencies exist, such as add_to_queue vs create_folder/create_print_job, save_queue_group vs update/create, and the slightly odd home_printer and send_back_for_revision.

Tool Count1/5

With 74 tools, this is far beyond the recommended MCP server size and makes the toolset unwieldy to navigate, even for a broad domain. This clearly falls into the extreme 50+ tool category.

Completeness3/5

Core operational workflows—queue, print jobs, files, filament, and printer control—are well represented. However, printer lifecycle management is missing (no add/update/delete printer), and maintenance management is limited to a read-only dashboard with no corresponding actions.

Resources