Skip to main content
Glama

3d-cad

stl_slice_to_gcode

Slice a 3D STL mesh across Z-planes with outer wall contours and rectilinear/grid infill into Marlin/Klipper G-Code.

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": "stl_slice_to_gcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathNo
base64DataNo
outputPathNo
printSpeedNo
layerHeightNo
infillDensityNo
infillPatternNolines

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It discloses useful behavior (Z-plane slicing, wall plus infill generation, Marlin/Klipper dialect), but omits whether a file is written to outputPath, overwrite/error behavior, performance characteristics, and how input is sourced.

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?

A single dense sentence that leads with the action and resource and ends with the output target. No filler, though the density trades readability for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter file-processing tool with no annotations and no output schema, the description leaves the input-source choice, output destination, units/defaults, and failure modes unexplained. It is not sufficient for an agent to invoke the tool reliably without trial.

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

Parameters3/5

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

Schema description coverage is 0%, so the description should compensate but largely does not; 4 of 7 parameters (inputPath, base64Data, outputPath, printSpeed) are unmentioned. It does add meaning for infillPattern (rectilinear/grid, matching the enum) and implies layerHeight via 'Z-planes', which is why this is not a 1.

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?

States a specific verb (slice) and resource (3D STL mesh) plus the transformation target (Z-planes, wall contours, infill) and output format (Marlin/Klipper G-Code). It is clearly distinguishable from siblings like cad_convert_to_stl or stl_heal, though it does not name them explicitly.

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

Usage Guidelines2/5

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

No guidance on when to use this versus cad_convert_to_stl/stl_heal, no prerequisites, and no hint about which of inputPath or base64Data to supply. The agent must infer the entire call context from the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources