Skip to main content
Glama

Slice Estimate

slice_estimate
Read-only

Estimate FDM print mass, filament length, layer count, and print time analytically from model volume and bounding box, without running a slicer.

Instructions

First-order FDM slice estimate (analytic, NO slicer needed; see slice_gcode_submit for the real PrusaSlicer CLI). mass_g = volume·density (Materials DB); deposited = volume·(wall_fraction + infill·(1−wall_fraction)) so at 100% infill filament_g == mass_g; layer_count = ceil(bbox height/layer_height); print_time from nozzle volumetric flow.

material may be any Materials-DB card name (material_list / material_get), or anything at all if you supply density_g_cc yourself — it overrides the DB lookup. A generic word like 'polymer' is a CATEGORY, not a card, and 'nylon' is a near-miss for one, so neither carries a density; the error names both exits. filament_dia_mm (1.75 default, 2.85 for the older standard) sets the spool stock the filament length is computed against.

Returns {mass_g, filament_g, deposited_volume_mm3, layer_count, print_time_min, infill_fraction}. Errors on a material with no density and no override, a negative volume, a bbox shorter than [x,y,z], or a non-positive layer height.

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": {
      "volume_mm3": "<volume_mm3>",
      "bbox_mm": "<bbox_mm>"
    },
    "name": "slice_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bbox_mmYes
materialNoPLA
nozzle_mmNo
workspaceNoRun this call in this named workspace
volume_mm3Yes
density_g_ccNo
wall_fractionNo
filament_dia_mmNo
infill_fractionNo
layer_height_mmNo
print_speed_mm_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only and closed-world behavior, and the description adds substantial context beyond them: the analytic formulas, material/density fallback behavior, filament diameter effect, return fields, and specific error conditions. There is no contradiction with the annotations.

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 description is front-loaded and dense, with the tool's purpose and sibling distinction stated first. It is longer than a typical description but most of the length is justified by formulas, material caveats, returns, and error conditions. Some parenthetical detail could be trimmed, but there is little obvious 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?

With no output schema and low schema description coverage, the description fills the important gaps: it lists return fields, documents error conditions, explains the material/density resolution rules, and distinguishes the analytic estimate from the real slicer. It is complete enough for an agent to invoke the 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 description coverage is only 9%, so the description must carry most parameter meaning. It does this well for the critical inputs — material, density override, filament diameter, volume, bbox, layer height, infill, wall fraction, and print speed — through formulas and defaults. It leaves minor gaps for parameters like `nozzle_mm` and `workspace`, but is far stronger than the schema alone.

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 first sentence states a specific verb and resource — a first-order FDM slice estimate — and immediately distinguishes it from `slice_gcode_submit` as the real slicer path. It also explains the analytic nature and formulas, so an agent can tell exactly what this tool computes.

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

Usage Guidelines4/5

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

It clearly points to `slice_gcode_submit` for the real PrusaSlicer CLI, implying this is the quick analytic alternative when no slicer is needed. It also explains material-selection alternatives via `material_list`/`material_get` and the density override. It stops short of a full explicit when-to-use/when-not-to-use statement across all estimate siblings.

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