Skip to main content
Glama

FabTally 3D-Print Slicer, Quote & DFM

by com.fabtally

Optimize 3D-print orientation (least support)

optimize_orientation

FREE (personal/interactive; fair-use limited — counts as ~4 slices). Orientation optimiser: really slices up to 4 candidate build orientations with automatic supports and recommends the one using the LEAST support material (exact, slice-derived), with the filament/time saved vs printing as-is and an estimated price. 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. Reduces support waste, print time and post-processing. Agents / high volume: prepaid credits or the x402 agent lane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden. It thoroughly discloses behavioral traits: free tier with fair-use limit counting as ~4 slices, actual slicing of up to 4 orientations with automatic supports, exact support material measurement, and output of filament/time saved plus estimated price. It also explains input handling (zip → first printable model, base64 truncation fallback) and the upload workflow, providing rich context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: cost/limitations, core function, input formats, fallback path, benefits, and enterprise use. It is front-loaded with the most critical info (cost and purpose). No fluff or redundancy.

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

Completeness4/5

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

Given there is no output schema, the description compensates by summarizing the output: recommendation, support material, filament/time saved, and estimated price. It covers input types, fallback, and cost. Minor gaps remain (e.g., error handling, max URL size limits) but overall it is sufficiently complete for a tool of this complexity.

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 coverage is 100%, so baseline is 3. The description adds extra meaning for model_url and model_base64 by explaining the upload flow, zip handling, and base64 truncation risks for MCP clients. It also clarifies that layer_height overrides quality. This exceeds the schema's descriptions, earning a 4.

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 clearly states the tool is an 'Orientation optimiser' that 'slices up to 4 candidate build orientations' and 'recommends the one using the LEAST support material (exact, slice-derived)'. This is a specific verb+resource with a clear scope, and it distinguishes itself from sibling tools like slice_model or check_printability by focusing on orientation optimization.

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 implies the use case: reduce support waste, print time, and post-processing. It also mentions fair-use limits and the x402 agent lane for high volume. However, it does not explicitly contrast with alternatives like slice_model or list when not to use it, so it stops short of full exclusion guidance.

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