Skip to main content
Glama
creator5-slicer-mcp

creator5-slicer-mcp

by rsutcliffe

recommend_settings

Selects filament, quality, strength, support, and brim settings for a 3D print without slicing, with reasoning for each choice.

Instructions

Choose presets and settings for a print without slicing, with the reasoning for each choice.

Args: filament: Filament as the user describes it, e.g. "black PLA", "PETG", "TPU 95A", "silk PLA". model_path: Optional absolute path to the STL, so supports and brim respond to its shape. quality: draft, standard or fine. Sets layer height and outer wall care. strength: decorative, standard, functional or structural. Sets walls, infill and shells. nozzle: Nozzle diameter in mm: 0.25, 0.4, 0.6 or 0.8. supports: auto, on or off. brim: auto, on or off. layer_height: Exact layer height in mm, or 0 to let quality decide. precise_fit: True for parts that must mate with other parts. smooth_top: True to iron flat top surfaces. pro: True for the Creator 5 Pro. nozzle_temp: Nozzle temperature in C from the spool's label, or 0 to use the preset. bed_temp: Bed temperature in C from the spool's label, or 0 to use the preset. max_speed: Fastest print speed in mm/s the spool's label recommends, or 0 for no extra limit.

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": {
      "filament": "<filament>"
    },
    "name": "recommend_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
proNo
brimNoauto
nozzleNo0.4
qualityNostandard
bed_tempNo
filamentYes
strengthNostandard
supportsNoauto
max_speedNo
model_pathNo
smooth_topNo
nozzle_tempNo
precise_fitNo
layer_heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose that the response is presets plus per-choice reasoning rather than sliced output. It does not state whether the tool reads the file at model_path, whether it mutates anything on disk, what happens on an unrecognized filament string, or whether it validates the model exists. Those omissions are meaningful for a 14-parameter tool with zero annotation coverage.

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?

The purpose sentence is front-loaded and the args block is dense and line-per-parameter, so scanning is easy and little is wasted. It is a raw docstring dump rather than prose tuned for an agent, but every argument line carries actionable information, so almost nothing could be cut without loss.

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 14-parameter, no-output-schema tool, the description covers the input surface thoroughly and tells the agent the return contains the chosen presets with reasoning per choice. Remaining gaps are the exact response shape and failure behavior for bad filament/nozzle input, which are secondary given how well the parameters are specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description documents every one of the 14 parameters with real meaning: it enumerates allowed values for quality, strength, nozzle, supports and brim, and explains the 0 sentinel for layer_height, nozzle_temp, bed_temp and max_speed as "let the preset decide." It also clarifies intent for the non-obvious booleans (precise_fit for mating parts, smooth_top for ironing, pro for the Creator 5 Pro) and explains why model_path matters (supports and brim respond to the shape). This is nearly all the semantic value an agent needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Choose presets and settings for a print without slicing, with the reasoning for each choice" gives a specific verb (choose presets/settings) and resource (print configuration), and the phrase "without slicing" implicitly separates it from slice_model and open_in_slicer. It stops short of naming or explicitly contrasting a sibling, so it lands at a clear-but-not-differentiating 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The "without slicing" clause hints this is the pre-slice configuration step, and the parameter list implies the workflow (describe filament, then get settings). However, there is no explicit statement of when to call this versus slice_model or open_in_slicer, and no prerequisites such as running list_filaments first or passing a valid model_path. Usage is left implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.