Skip to main content
Glama
SlicerBridge

SlicerBridge

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

SlicerBridge converts a multicolor .3mf project, saved by Bambu Studio, OrcaSlicer or a maker's fork of either (Creality Print, ElegooSlicer, Anycubic Slicer Next, Flash Studio, QIDI Studio), into a ready, checked file for each multicolor printer (Bambu Lab, Creality, Elegoo, Anycubic, Flashforge, QIDI, WonderMaker, Prusa, Snapmaker U1). Start with inspect_model to see the colors a model uses and how it fits each bed, then convert_model. A file SlicerBridge wrote can go back in for another printer. PrusaSlicer projects aren't read yet. A file that fails a check is never written; the result says why. Paths are on the user's machine.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_printersB

Every printer SlicerBridge writes for: its key, name, engine, slicer, the colors it holds, the filament types it takes (any other is refused), and the sets it's in.

inspect_modelA

Describe a multicolor .3mf project: its palette, the filament slots it actually uses, each plate's size, and whether it fits each printer's bed (and at what scale if not).

convert_modelA

Write a ready file per printer for a multicolor .3mf project (from Bambu Studio, OrcaSlicer, a maker's fork, or a file SlicerBridge wrote), each one checked before it is kept. Files go in <out_dir>//, named ' - .3mf', or ' - - .3mf' with a suffix. A printer the model can't go to (more colors than it holds, an unknown filament type) is refused with the reason; nothing wrong is written.

verify_filesA

Re-run SlicerBridge's checks on files it wrote (colors, paint, plates, size, settings), and optionally slice each one.

brand_checkA

Slice each file in the slicer its printer's maker ships (Creality Print, ElegooSlicer, Anycubic Slicer Next, Flash Studio, QIDI Studio), where installed, and report what that slicer makes of it.

doctorB

Which slicers SlicerBridge finds, their versions, and where it keeps its templates.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation4/5

Most tools target a clearly distinct phase of the workflow: list_printers (discovery), inspect_model (input analysis), convert_model (output writing), doctor (environment diagnostics). brand_check and verify_files both revolve around checking/slicing files, which could cause occasional misselection, though the descriptions distinguish third-party slicer comparison from re-validating SlicerBridge's own output.

Naming Consistency4/5

Five of six tools follow a clean verb_noun snake_case pattern (brand_check, verify_files, list_printers, convert_model, inspect_model). 'doctor' is a bare noun diagnostic command, a minor deviation from the otherwise consistent convention.

Tool Count5/5

Six tools is well-scoped for a slicer bridge: discovery, inspection, conversion, verification, brand comparison, and diagnostics each earn a distinct place. Nothing feels padded or missing at this count.

Completeness4/5

The core lifecycle is covered: list printers, inspect a model, convert it, then verify the written files, with doctor and brand_check as supporting operations. Minor gaps exist around managing/registering printers or templates and cleaning up old outputs, but agents can work around these for the stated purpose.

Maintenance

ActivityNo data
ResponsivenessOutdated data