Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save preset (overwrites stored settings)

save_preset
Destructive

Save current OrcaSlicer settings as a named print, filament, or printer preset—or update an existing one—so the profile appears in the GUI immediately and can be reused.

Instructions

Save the current settings as a named user preset; edit_preset changes a stored preset in one step instead.

It creates or updates the preset, visible in the GUI immediately. type = print|filament|printer. detach=True saves it standalone instead of inheriting the current base preset; use it when creating a filament preset for a DIFFERENT material than the one selected, otherwise the new preset inherits the base's filament_type and temperatures.

Run check_profile_physics first; do not save when verdict=blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "name": "<name>"
    },
    "name": "save_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYes
detachNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is covered; the description adds value beyond that with the overwrite-vs-create semantics, immediate GUI visibility of the result, the inheritance behavior controlled by detach, and a blocking precondition (verdict=blocked). That inheritance detail is non-obvious and materially changes the outcome of a call.

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 purpose and the sibling alternative, then progressively more specific conditions; every clause carries operational information. It is dense for three parameters and the detach explanation runs long, but nothing is redundant with the schema or annotations.

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?

For an overwriting mutation with no output schema and 0% schema coverage, the description supplies the enum values, inheritance semantics, visibility of the effect, the recommended verification step, and the blocking condition. An agent has everything needed to call it correctly and know when not to.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameters, and it does: the type enum is spelled out as print|filament|printer, detach is explained functionally with the exact scenario that requires it, and name is tied to "named user preset." All three parameters gain meaning absent from the bare 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?

States a specific verb and resource ("Save the current settings as a named user preset") plus the create-or-update scope, and explicitly contrasts with the sibling edit_preset in the same sentence. An agent can distinguish this from edit_preset, rename_preset, and save_project 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?

Gives explicit routing (use edit_preset to change a stored preset in one step), a conditional rule for detach=True with the failure mode if you don't (wrong filament_type and temperatures inherited), and a hard prerequisite/gate: run check_profile_physics first and do not save when verdict=blocked. This is when-to-use, when-not-to-use, and ordering in one place.

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