Skip to main content
Glama

FabTally 3D-Print Slicer, Quote & DFM

by com.fabtally

Check 3D-print printability (DFM)

check_printability

FREE 3D-printing DFM / printability check for an STL/3MF/OBJ/PLY model. Paste a link: Thingiverse/Printables/MakerWorld model pages, a GitHub blob, Google Drive or Dropbox share link, a direct .stl/.3mf/.obj/.ply/.step URL, or a .zip (first printable model inside is used). Local file? Upload once at https://fabtally.com/upload and paste that URL. Default (full=false): a fast geometry-only read — printable verdict (yes/with-warnings/no), watertight/manifold, dimensions & volume, fits-on-bed, wall-thickness estimate vs the 0.4mm nozzle, overhang heuristic. Set full=true for the complete report with EXACT support-material grams/time and infill material-saving deltas from REAL slices (every field labelled exact vs heuristic). Both are FREE for personal/interactive use (fair-use limits); agents/high-volume use prepaid credits or the x402 lane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNofalse (default) = fast geometry-only read. true = full report with exact slice-derived support & material deltas (free for interactive use; counts toward the daily fair-use limit).
printerNoPrinter id from list_printers (elegoo-neptune4-max, bambu-a1, bambu-a1-mini, bambu-p1s, bambu-x1c, prusa-mk4, prusa-mini, ender3-v3, creality-k1, creality-k1-max, voron-24-350, anycubic-kobra2). Default elegoo-neptune4-max.
qualityNoQuality preset: draft 0.28mm | standard 0.20mm | fine 0.12mm layer height.
filenameNoFile name incl. extension, e.g. 'bracket.stl'. Required with model_base64.
materialNoFilament/material id (pla, pla-cf, petg, petg-cf, abs, abs-cf, asa, asa-cf, nylon, pc, pet, tpu). Default pla.
model_urlNoPREFERRED. Public URL to the 3D model. Paste a link: Thingiverse/Printables/MakerWorld model pages, a GitHub blob, Google Drive or Dropbox share link, a direct .stl/.3mf/.obj/.ply/.step URL, or a .zip (first printable model inside is used). Local file? Upload once at https://fabtally.com/upload and paste that URL. The server fetches and (if a zip) unpacks it.
layer_heightNoExplicit layer height mm (0.04-0.6); overrides `quality`.
model_base64NoBase64 model bytes — small-file fallback only (roughly <50KB). MCP clients (Claude/ChatGPT Desktop) truncate large inline tool arguments, so a real STL can silently arrive corrupted. For anything bigger use model_url (upload at https://fabtally.com/upload first). Provide `filename` too.
infill_percentNoSparse infill density percent (0-100).

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals important traits: fair-use limits, exact vs heuristic labels in the full report, zip handling (first printable model), base64 corruption risk, and the need to upload local files. This is exceptionally transparent for an API consumer.

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 long but information-dense; every sentence adds value. It is front-loaded with the core purpose and then systematically covers input methods, modes, and limitations. Slight verbosity around the fair-use policy and upload steps could be trimmed, but overall it is well-structured for a complex tool.

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?

Given 9 parameters, no output schema, and no annotations, the description is remarkably complete. It explains what the tool returns in both default and full mode (verdict, watertight, dimensions, etc.), covers all input formats including zip and local files, and clarifies parameter dependencies like layer_height overriding quality. The agent can invoke this tool with confidence.

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?

Although the schema already has 100% coverage, the description adds significant meaning beyond it. For example, it explains that 'model_url' is preferred, details how zip files are processed, warns about base64 truncation in MCP clients, and clarifies the 'full' parameter's effect. This enriches the agent's understanding of parameter nuances.

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 description opens with a specific verb+resource: 'FREE 3D-printing DFM / printability check for an STL/3MF/OBJ/PLY model.' This clearly states what the tool does and distinguishes it from sibling tools like slice_model or validate_model by focusing on printability/DFM checks, supported formats, and link-based input.

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?

The description provides clear context on when to use the default fast mode vs full=true, as well as usage policy (free for personal/interactive use vs prepaid credits for agents). It also explains preferred input methods (model_url vs model_base64). However, it does not explicitly compare against sibling tools or state when NOT to use this tool, so it falls short of the top score.

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

All FabTally 3D-Print Slicer, Quote & DFM toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Four tools—analyze_model, analyze_3d_model, check_printability, and validate_model—perform overlapping geometry analysis with printability verdicts, making it hard to tell which to call. The detailed descriptions help, but the boundaries are subtle (general vs printing-specific, full vs fast), and an agent could easily pick the wrong one.

Naming Consistency4/5

Most names follow a clear verb_noun snake_case pattern (e.g., list_printers, slice_model, get_print_quote). Minor deviations like analyze_3d_model, cost_breakdown, scale_advisor, and whatif_infill are still readable and do not break the overall consistency.

Tool Count4/5

With 14 tools, the count is well within the 3–15 range for a specialist service and each tool addresses a distinct stage of the quoting/DFM workflow. The count feels slightly inflated by the near-duplicate analysis cluster, but it is not excessive for the domain.

Completeness4/5

The tool surface covers the full lifecycle: model analysis, printability checks, slicing, quoting, cost breakdown, printer comparison, orientation optimization, material/settings recommendations, and scaling. Minor gaps exist (e.g., no batch processing or material-specific parameter tuning), but agents can compose the existing tools to achieve most workflows.

Resources