Skip to main content
Glama
MaxEllis

orcaslicer-mcp

by MaxEllis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set height-range config

set_height_range

Set a custom layer height on any vertical band of a model to add finer detail where needed. Accepts min/max Z and layer height, or clears all bands.

Instructions

Override the layer height over a Z band of one object (e.g. 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.

Input Schema

TableJSON 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.9/5.0
Behavior5/5

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

The description discloses behaviors beyond the annotations: passing the same min_z/max_z updates the band, clear=True removes every band, and bands invalidate the last slice requiring re-slicing. The annotations only declare readOnlyHint=false and destructiveHint=false, so the description adds meaningful side-effect context without contradicting them.

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 compact and front-loaded with the core behavior, followed by update/clear semantics, side effects, and an alternative tool. Every sentence carries operational value with no filler.

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?

Despite no output schema and sparse annotations, the description covers the object id source, band semantics, clear behavior, side effect on slicing, and the correct alternative tool. Together with 100% schema coverage, an agent has everything needed to call this tool correctly.

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 the baseline is 3. The description adds extra semantics by explaining the relationship between parameters: passing the same min_z/max_z updates an existing band, and clear=True removes all bands. This goes beyond the schema's individual field descriptions.

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 states a specific verb and resource: 'Override the layer height over a Z band of one object', with a concrete example. It also explicitly distinguishes itself from set_layer_height, making the tool's scope immediately clear.

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 gives explicit when-to-use context ('For a single height across the whole object use set_layer_height instead'), tells the agent to re-slice after use, and directs where to get the object id from list_objects. This fully routes the agent to the correct call.

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