Skip to main content
Glama
MaxEllis

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set config values

set_config

Apply config changes to the active project as unsaved overrides, atomically: if any key is invalid the whole batch is rejected and nothing changes. Returns {applied, errors}.

Instructions

Apply config changes to the active project as unsaved overrides, atomically: if any key is invalid the whole batch is rejected and nothing changes. Returns {applied, errors}.

Overrides show as modified in get_status, are not written to any preset file, and revert if the preset is reselected; call save_preset to persist them. Each apply invalidates the last slice, so re-slice afterwards. It does not run the physics gate, so for temperature, speed, acceleration, or flow keys run check_profile_physics before trusting the result. To edit a stored preset rather than the live project, use edit_preset.

On a multi-filament setup do filament edits before print edits: changing another slot's value means select_preset for that slot, which discards unsaved print overrides (docs/order-of-operations.md).

Input Schema

NameRequiredDescriptionDefault
changesYesMap of OrcaSlicer config key to new value, e.g. {'layer_height': 0.2, 'sparse_infill_density': '15%'}. Values must match each setting's type; percent settings take strings like '15%'. Discover valid keys with search_settings, find_config_keys, or describe_setting. Do NOT echo back a get_config value for a per-filament setting (hot_plate_temp, fan_min_speed, nozzle_temperature_initial_layer, ...): get_config reports those merged across every loaded filament ('70,100,70,70,35'), while this writes the one filament preset open in the Filament tab, so pass that preset's single value instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / changes / description
      Previous value: -"Map of OrcaSlicer config key to new value, e.g. {'layer_height': 0.2, 'sparse_infill_density': '15%'}. Values must match each setting's type; percent settings take strings like '15%'. Discover valid keys with search_settings, find_config_keys, or describe_setting."New value: +"Map of OrcaSlicer config key to new value, e.g. {'layer_height': 0.2, 'sparse_infill_density': '15%'}. Values must match each setting's type; percent settings take strings like '15%'. Discover valid keys with search_settings, find_config_keys, or describe_setting. Do NOT echo back a get_config value for a per-filament setting (hot_plate_temp, fan_min_speed, nozzle_temperature_initial_layer, ...): get_config reports those merged across every loaded filament ('70,100,70,70,35'), while this writes the one filament preset open in the Filament tab, so pass that preset's single value instead."
  2. Changed1 schema field changedv0.1.10
    • addedInput schema / properties / changes / description
      Added value: +"Map of OrcaSlicer config key to new value, e.g. {'layer_height': 0.2, 'sparse_infill_density': '15%'}. Values must match each setting's type; percent settings take strings like '15%'. Discover valid keys with search_settings, find_config_keys, or describe_setting."
  3. First observedv0.1.8

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly=false and destructive=false; the description carries the real behavioral burden and does it well. It discloses atomic all-or-nothing rejection, that overrides are not written to preset files and revert on preset reselection, that each apply invalidates the last slice, and that the physics gate is NOT run.

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?

Front-loaded with the core action and atomicity guarantee, then layered with the caveats an agent actually needs. It is dense and slightly long, but nearly every sentence earns its place; only minor tightening would help.

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

Completeness5/5

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

There is no output schema, yet the description specifies the return shape ({applied, errors}) and covers persistence, revert, slice-invalidation, physics-gate, and multi-filament ordering concerns. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the 'changes' property already has extensive inline documentation (type matching, percent-string format, discovery tools, the per-filament echo-back caveat), so the schema does the heavy lifting. The description adds only the batch-rejection behavior tied to invalid keys, which is useful but marginal against an already-complete schema.

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 states a specific verb and resource ('Apply config changes to the active project as unsaved overrides') and immediately distinguishes this tool from its closest siblings by naming edit_preset and save_preset. An agent can tell it apart from those without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing rules are given: use edit_preset to change a stored preset rather than the live project, call save_preset to persist, and run check_profile_physics before trusting temperature/speed/acceleration/flow changes. The multi-filament ordering prerequisite (filament edits before print edits, per docs/order-of-operations.md) is likewise spelled out.

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

Deploy Server

Other Tools