Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get project file state

get_project
Read-only

Read the current OrcaSlicer project state—name, path, unsaved changes, saved status, plate/object counts, and modified presets—before saving, opening, or creating a project.

Instructions

Read the open project as a file (name, path, unsaved changes); check it before save_project, open_project or new_project.

Also reports whether it has been saved, plate and object counts, the preset groups with unsaved edits (modified) and how many entries File > Recent holds; path is empty until the first save. Read-only. 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": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.21

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true, so the bar is lower, yet the description still adds non-obvious behavior: path stays empty until the first save, and the tool requires fork v2.4.2-mcp.15 or later. The "Read-only" restatement is redundant with the annotation, but the version gate and empty-path semantics are genuine added context.

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 core action and the call-order advice, then a second block detailing the report contents. The parenthetical and the enumerated return data are dense but each clause carries information; only the "Read-only" sentence is largely wasted against the annotation.

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?

There is no output schema, so the description must describe what comes back, and it does so thoroughly: file identity, saved state, plate and object counts, modified preset groups, and recent-entry count. Combined with the version requirement, an agent has everything needed to call it correctly and interpret the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description's listing of returned fields is complementary rather than a substitute for parameter documentation.

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 ("Read the open project as a file") and enumerates the fields returned (name, path, unsaved changes, saved status, plate/object counts, modified preset groups, recent entry count). It explicitly contrasts itself with the mutating siblings save_project, open_project and new_project, so an agent can separate it from them without opening schemas.

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?

"check it before save_project, open_project or new_project" gives a concrete call-order rule and names the tools it precedes, which is real when-to-use guidance. It does not state a when-not-to-use case or an alternative read path (e.g. browsing on-disk project files), so it falls short of full routing guidance.

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