Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

New project (replaces the open session)

new_project
Destructive

Start a new, empty OrcaSlicer project without a dialog, choosing how to handle unsaved changes. Follow with load_model and save_project to create the project file.

Instructions

Start a new, empty project (File > New Project) without a dialog.

The unsaved-changes prompt is answered by if_unsaved. OrcaSlicer's second prompt, keep or discard modified presets, is answered with Keep: unsaved preset overrides carry over into the new project and the reply names them in kept_changes (select_preset drops them if that is not wanted). Follow with load_model and save_project to create a project file. Needs fork v2.4.2-mcp.15 or later.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "new_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA title for the new project, shown in the window; 'Untitled' when omitted. The file name is chosen when save_project is called with a path.
if_unsavedNoWhat to do when the current project has unsaved changes: 'fail' (default) refuses and changes nothing, 'save' writes it to its own path first (fails with no_project_path if it has none), 'discard' throws the changes away.fail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.21

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description builds on that by naming exactly what is replaced (the open session) and how the unsaved-changes choice affects the outcome, including the no_project_path failure for 'save'. The subtle preset-override carry-over and its interaction with select_preset is behavior an agent could not infer from annotations.

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?

Front-loaded with the action, then the two prompt resolutions, then the recommended follow-up and the version requirement. Every sentence carries operational information (prompt handling, preset carry-over, fork version), with no 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?

Covers the destructive replacement, both dialog answers, the follow-on call sequence, and a return-value detail (kept_changes) even though no output schema exists. The minimum fork version is also stated, leaving nothing material for an agent to guess.

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%, so both parameters are already documented; the description mainly reinforces if_unsaved behavior that the schema already spells out. It does add one non-obvious consequence beyond the schema: the keep-or-discard preset prompt is hard-wired to Keep, and the affected overrides are reported in kept_changes.

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 ('Start a new, empty project') and anchors it to the GUI equivalent (File > New Project, no dialog). It also names the replacement effect on the current session, which separates it from open_project/open_recent_project.

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 follow-up sequencing ('Follow with load_model and save_project to create a project file') and explains that the unsaved-changes prompt is resolved via if_unsaved. It does not explicitly exclude opening an existing project with open_project, but the create-new context is unambiguous.

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