MCP server intelligent pour PrusaSlicer — analyse mesh, recommandation de profils, slicing
PrusaMCP has 17 tools with reasonable naming (verb-first) and descriptions, but significant gaps in parameter documentation and output schema specification prevent higher scores. Most tools lack detailed parameter descriptions and none have explicitly documented output schemas. While tool names are generally action-oriented (analyze-mesh, check-printability, recommend-profile), parameter documentation is minimal, many params have one-liner descriptions that don't meet the 10-1024 char baseline or fail to specify constraints, formats, or dependencies. For example, 'recommend-profile' accepts a 'goal' parameter described only as 'Print goal: prototype rapide, beau rendu, or detail' but doesn't declare this as an enum constraint in the schema. No tools provide structured output documentation, making it impossible to verify that chains of tools can pass required IDs and references to downstream calls. Error handling is not visible in the provided code samples, no recovery guidance, categorization, or actionable error messages. Security is a concern: 'upload-print' accepts a 'destination' as a free string (could be any IP or service), and 'generate-config' writes files to arbitrary paths, both without apparent input validation. File path parameters (stl_path, output_path, gcode_path) are not validated for path traversal.
Analyse mesh geometry: volume, surface area, overhangs, manifold check, small details detection
Check printability issues: overhangs, thin walls, small details, manifold issues
Diagnose print issues based on print results and feedback data
Estimate print cost from mesh analysis or G-code stats (filament, electricity, time)
Export local feedback as anonymized community data
Get statistics from local feedback store: success rate, common issues, best settings by material
Generate PrusaSlicer .ini configuration file from a recommended profile
Get current model path and settings from PrusaSlicer
No tool output schemas documented. Callers cannot determine what fields to extract or pass to downstream tools. Example: 'recommend-profile' returns a RecommendedProfile object, but this structure is never defined in tool metadata.
Enum constraints not declared in schemas. 'recommend-profile' goal param accepts 'prototype rapide', 'beau rendu', 'detail' but these are free-form strings with no enum in the schema. LLMs will hallucinate alternatives.
File path parameters lack input validation and traversal guards. 'stl_path', 'output_path', 'gcode_path' are passed directly, no sanitization visible for ../ sequences or symlink attacks.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 37 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 34 | - | v1 |
Post-process G-code: add custom commands, adjust speeds, add comments
Interactive print wizard: step through printer, nozzle, material selection and generate profile
Recommend print profile based on printer model, nozzle size, goal (speed/quality/detail), material, and mesh analysis
Take a screenshot of current PrusaSlicer window
Search filament database by material, brand, or query
Slice STL model using PrusaSlicer console with generated profile
Submit print feedback to local store: model name, material, settings, scores, issues
Suggest optimal print orientations based on overhangs, support volume, print height, and bed contact
Upload G-code to printer or cloud service
Parameter descriptions too generic or missing constraint details. Examples: 'destination' in upload-print is described only as 'Destination: printer name, IP, or cloud service', no format, validation, or enum. 'adjustments' in postprocess-gcode is 'Optional speed adjustments, custom commands' with no schema.
No error handling visible. No recovery guidance, categorization (retryable vs fatal), or actionable messages. If 'analyze-mesh' fails on malformed STL, the agent has no guidance on what to try next.
Tool composition risks: 'recommend-profile' returns an object that 'generate-config' and 'slice' consume, but output schema for 'recommend-profile' is not documented. Chain will break if schema changes.
print-wizard tool design unclear. 'step' parameter accepts 'start, printer, nozzle, material, goal, review' as free strings with no enum. 'previous_responses' is an untyped object, schema does not specify what keys/structure the agent should pass.
No destructive operation warnings or confirmation patterns. 'generate-config', 'postprocess-gcode', 'slice', and 'upload-print' all modify or overwrite files without dry-run or confirmation support.