Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set layer height

set_layer_height

Toggle adaptive layer height for a selected object: enable it with a quality value for finer detail, or reset it to restore uniform layer heights.

Instructions

Turn adaptive layer height on or off for one object; set_height_range sets a fixed height over a Z band instead.

mode='adaptive' (quality 0..1, higher = finer detail) generates an adaptive profile; mode='reset' (aliases: 'default', 'none') restores uniform layers.

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": {
      "object_id": "<object_id>",
      "mode": "<mode>"
    },
    "name": "set_layer_height"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
qualityNo
object_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already state this is a non-read-only, non-destructive mutation; the description adds that adaptive mode generates a profile and reset restores uniform layers, clarifying the state change. It does not cover permissions, idempotency, or error behavior, so it is strong but not exhaustive.

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?

The description is three short lines, front-loads the core action and alternative, and each sentence adds useful mode or parameter semantics. There is no filler.

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?

For a three-parameter mutation with no output schema, the description covers the main action, the alternative tool, and both mode and quality semantics. It is somewhat thin on object_id handling and post-call results, but the remaining gaps are minor.

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 0%, so the description must carry parameter meaning; it documents the mode values and aliases and defines quality as 0..1 with higher meaning finer detail. It only implicitly covers object_id as 'one object' and omits its expected format or existence requirements.

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?

The description opens with a specific verb and resource: turning adaptive layer height on or off for one object. It also explicitly distinguishes the tool from set_height_range, so an agent can identify its scope without opening the 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?

It names set_height_range as the alternative for fixed height over a Z band, and it explains the two mode values: adaptive for an adaptive profile and reset/default/none for restoring uniform layers. That gives clear when-to-use and mode-selection 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