Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List project files in a folder

browse_projects
Read-only

Lists .3mf project files in a chosen OrcaSlicer folder, newest first, so you can find a project to open or choose an unused save name.

Instructions

List the .3mf project files in one folder on the OrcaSlicer machine; list_recent_projects shows File > Recent instead.

Not recursive, newest first: path, project name, size and last-modified time, and whether each is the open project. Read-only. Use it to find a project to open_project, or to pick a free name before save_project. 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": "browse_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoA folder on the OrcaSlicer host. None uses the open project's folder, or the folder OrcaSlicer's last file dialog used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.21

TDQS

A4.5/5.0
Behavior4/5

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

Adds real context beyond readOnlyHint=true: non-recursive scope, newest-first ordering, the exact returned fields including the open-project flag, and a prerequisite (fork v2.4.2-mcp.15 or later). The only omission is behavior on a nonexistent or unreadable folder path, so it falls just short of full disclosure.

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 and scope, then the sibling exclusion, then the return shape and prerequisites. No sentence is filler despite packing in sorting, return fields, and a version requirement.

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 single-optional-parameter read tool with no output schema, the definition covers scope, ordering, return fields, read-only nature, alternative tool, downstream use, and minimum fork version. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100% and the single dir parameter already documents its null default thoroughly. The description contributes only 'in one folder', which doesn't expand on path format or error behavior, so the baseline 3 applies.

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 (list the .3mf project files), scopes it to a single folder on the OrcaSlicer machine, and explicitly separates it from list_recent_projects (File > Recent). An agent can distinguish it from the sibling without opening 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 both a when-to-use and the downstream step: find a project to open_project, or pick a free name before save_project. It also names the sibling to use instead for recent-file browsing, so the alternative path is explicit rather than inferred.

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