Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Remove an entry from recent projects

forget_recent_project

Remove a file from OrcaSlicer's Recent list by path or index, or clear the entire list without deleting files from disk. Use it after files are moved or deleted outside the app.

Instructions

Remove an entry from File > Recent, or clear the list; the file on disk stays.

By path or index. Useful after a file was deleted or moved outside OrcaSlicer. The reply names what was forgotten and returns the list as it is now. 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": "forget_recent_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoClear the whole list instead.
pathNoThe entry's path as list_recent_projects shows it (any spelling of the same file works while the file exists).
indexNoAlternatively, the entry's 0-based index from list_recent_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.21

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description earns credit for explaining WHY it is non-destructive ('the file on disk stays') and for describing the reply ('names what was forgotten and returns the list as it is now'). It does not cover failure/error behavior or what happens when no selector is supplied despite 0 required parameters.

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?

Four short sentences, front-loaded with the action and its scope, then selection mode, motivation, reply shape, and version requirement. Nothing is padded or repeated.

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 effect, selection, motivation, response, and a version prerequisite, which is close to full for a 3-optional-parameter tool with no output schema. The gap is the unspecified no-argument case: with 0 required params the description never says what a call passing none of all/path/index does.

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% and every parameter (all, path, index) is already described in the schema, so the baseline is 3. The description adds a small amount by framing path and index as alternative selectors ('By path or index'), but introduces no format or precedence detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Remove an entry from File > Recent, or clear the list') and immediately scopes the effect with 'the file on disk stays.' That clause implicitly separates it from file-deletion siblings such as delete_project_file, though no sibling is named outright.

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 a concrete triggering situation ('Useful after a file was deleted or moved outside OrcaSlicer') and the two selection modes. It stops short of naming alternatives like open_recent_project or stating that listing first via list_recent_projects is the intended precondition.

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