Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Open a recent project (replaces the open session)

open_recent_project
Destructive

Open a recently used OrcaSlicer project by its 0-based position in the File > Recent list. List recent projects first and open it immediately, since saves or opens reorder the list.

Instructions

Open an entry of File > Recent by its position in list_recent_projects; open_project takes a path instead.

Same behaviour and arguments as open_project. The list can change between calls (a save or an open moves its file to the top), so list first and open straight after; a file no longer on disk answers file_not_found and forget_recent_project removes the entry. Needs fork v2.4.2-mcp.15 or later.

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": {
      "index": "<index>"
    },
    "name": "open_recent_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes0-based position in list_recent_projects (0 is the most recent).
presetsNo'project' (default) selects the presets stored in the project; 'keep_current' selects the presets active before the call again.project
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, '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?

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true) by disclosing the real hazard: the recent list mutates between calls and a missing file yields file_not_found. It also states a hard version prerequisite (fork v2.4.2-mcp.15+), which is behavior an agent cannot get from structured fields. It stops short of warning about the unsaved-changes default ('fail') destroying anything, leaving that to the schema.

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-loads the core identification and the sibling contrast in the first sentence, then layers workflow, error handling, and version prerequisite. The parenthetical about saves moving files to the top is dense but earns its place; a few clauses could be tightened.

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 the workflow ordering, the error case, the cleanup tool, and a version gate for a mutation tool with no output schema. What remains thin is the unsaved-changes risk, which the annotations flag as destructive but the description never ties to the 'if_unsaved' default.

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 both enums are fully documented, so the baseline is 3. The description adds only a cross-reference ('same behaviour and arguments as open_project') and a freshness constraint on index; it does not explain 'presets' or 'if_unsaved' beyond what the schema already says.

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 ('Open an entry of File > Recent') and pins the argument's source ('by its position in list_recent_projects'), then explicitly contrasts with open_project, which 'takes a path instead.' An agent can distinguish this from its closest sibling without reading either 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 an explicit sequencing rule ('list first and open straight after') and names the alternative plus the condition that selects it (open_project for paths). It also names forget_recent_project for the stale-entry case, covering when-not/how-to-recover guidance, not just when-to-use.

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