Skip to main content
Glama
Sign In
orcaslicer-mcp

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set height-range config

set_height_range

Set a layer height for a specific Z band on one object to vary detail by height; clear bands when done, then re-slice.

Instructions

Set a layer height over a Z band of one object; set_layer_height makes the whole object adaptive instead.

For example 0 to 5 mm printed at 0.1 mm for finer detail near the base. Passing the same min_z and max_z again updates that band's height; clear=True removes every band on the object.

Bands are per-object and invalidate the last slice, so re-slice afterwards. For a single height across the whole object use set_layer_height instead. Get the id from list_objects.

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>"
    },
    "name": "set_height_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoIf True, remove all height-range overrides on the object and ignore the z and layer_height args.
max_zNoUpper Z bound of the band in mm. Required unless clear=True.
min_zNoLower Z bound of the band in mm (object-relative). Required unless clear=True.
object_idYesInteger id of the target object, from list_objects.
layer_heightNoLayer height in mm to use within the band, e.g. 0.1. Required unless clear=True.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.10
    • addedInput schema / properties / clear / description
      Added value: +"If True, remove all height-range overrides on the object and ignore the z and layer_height args."
    • addedInput schema / properties / layer_height / description
      Added value: +"Layer height in mm to use within the band, e.g. 0.1. Required unless clear=True."
    • addedInput schema / properties / max_z / description
      Added value: +"Upper Z bound of the band in mm. Required unless clear=True."
    • addedInput schema / properties / min_z / description
      Added value: +"Lower Z bound of the band in mm (object-relative). Required unless clear=True."
    • addedInput schema / properties / object_id / description
      Added value: +"Integer id of the target object, from list_objects."
  2. First observedv0.1.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds substantive behavior beyond that: bands are per-object, they invalidate the last slice, and a re-slice is required afterwards. It also explains that re-supplying the same min_z/max_z updates an existing band rather than stacking a duplicate. It does not cover edge cases such as overlapping bands or min_z > max_z.

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 key sibling differentiation in the first line, with the example and caveats following. Minor redundancy: the set_layer_height alternative is stated twice, and 'Get the id from list_objects' repeats what the object_id schema description already says.

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 5-parameter mutation tool with no output schema, the definition covers purpose, alternative, mutation side effects (slice invalidation), and removal semantics. The remaining gap is failure modes and constraints on the Z range, which an agent might want before calling.

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%, so baseline is 3, but the description adds real meaning: a concrete 0–5 mm at 0.1 mm example, the band-update semantics of repeated min_z/max_z, and the fact that clear=True ignores the z and layer_height arguments. That is useful interpretation beyond the schema text.

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 ('Set a layer height over a Z band of one object') and immediately distinguishes it from the sibling set_layer_height, which applies adaptively to the whole object. An agent can select it 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?

Gives explicit when-to-use ('0 to 5 mm printed at 0.1 mm for finer detail near the base'), names the alternative and its condition twice ('set_layer_height makes the whole object adaptive instead' / 'For a single height across the whole object use set_layer_height instead'), and covers the removal case via clear=True. Little is left to inference.

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