Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Rename preset

rename_preset

Renames a user preset by copying it to a new name, selecting the copy, and deleting the original; system presets remain read-only.

Instructions

Rename one of the user's presets; the renamed preset becomes the selected one.

It copies the preset to new_name, selects the copy and deletes the original. System presets are read-only.

Because it selects the renamed preset, this leaves it active and discards unsaved config overrides, the same as select_preset, and leaves the last slice invalid, so re-slice afterwards.

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>",
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesPreset group: 'print', 'filament', or 'printer'.
new_nameYesNew name for the preset. Should not collide with an existing preset of the same type.
old_nameYesCurrent name of the user preset to rename, as shown by list_presets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.10
    • addedInput schema / properties / new_name / description
      Added value: +"New name for the preset. Should not collide with an existing preset of the same type."
    • addedInput schema / properties / old_name / description
      Added value: +"Current name of the user preset to rename, as shown by list_presets."
    • addedInput schema / properties / type / description
      Added value: +"Preset group: 'print', 'filament', or 'printer'."
  2. First observedv0.1.8

TDQS

A4.6/5.0
Behavior5/5

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

With only readOnlyHint and destructiveHint supplied, the description carries real weight and delivers: it discloses the copy-select-delete mechanics, the loss of unsaved config overrides, and that the last slice becomes invalid. These are exactly the side effects an agent cannot infer from annotations, including one (discarding unsaved overrides) that is not obvious from the rename framing.

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 action and its main side effect, then prerequisites, then the required follow-up. The third paragraph restates the selection side effect already given in the first line, which is mild redundancy, but no sentence is filler.

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 a three-parameter mutation with no output schema, everything an agent needs is present: scope, restrictions, destructive side effects, and a mandated follow-up action. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: new_name receives a copy of the preset rather than an in-place edit, and old_name must refer to a user preset (system presets are read-only). That materially changes how an agent should construct the call.

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 ('Rename one of the user's presets') and immediately discloses the non-obvious side effect that the renamed preset becomes selected. This distinguishes it from edit_preset and select_preset without the agent needing to open 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 Guidelines4/5

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

Gives explicit constraints (system presets are read-only), prefers an implementation detail the agent must plan around (copy, select, delete), and prescribes a follow-up action ('re-slice afterwards'). It references select_preset as the behavior it shares, but never explicitly says when to pick rename over edit_preset, so it stops short of a full when/when-not routing statement.

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