Skip to main content
Glama

FabTally 3D-Print Slicer, Quote & DFM

by com.fabtally
OverviewDiscussionsAdmin

Recommend slice settings for a goal

recommend_settings

FREE. Suggest layer height / infill / walls for a goal (strength | speed | surface | cost) and slice WITH those settings so you see the resulting time / filament / cost. Paste a link: 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). Thingiverse/Printables/MakerWorld pages usually block server downloads: download the file yourself and upload it. Local file? Upload once at https://fabtally.com/upload and paste that URL. Fair-use limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesWhat to optimise for.
marginNoBYO pricing: fractional margin, 0.3 = 30%.
printerNoPrinter id from list_printers (elegoo-centauri-carbon, 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-centauri-carbon.
currencyNoBYO pricing: currency code (USD, EUR, ...). Default USD. Only a label: amounts are NOT converted, so pass your own rates in that currency too.
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.
quantityNoNumber of parts (1-10000). Volume discounts apply. Default 1.
model_urlNoPREFERRED. Public URL to the 3D model. Paste a link: 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). Thingiverse/Printables/MakerWorld pages usually block server downloads: download the file yourself and upload it. Local file? Upload once at https://fabtally.com/upload and paste that URL. The server fetches and (if a zip) unpacks it.
setup_feeNoBYO pricing: flat setup fee, charged once per job (not per part).
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.
minimum_priceNoBYO pricing: per-unit price floor, applied after volume discounts.
markup_percentNoBYO pricing: extra % markup on top of margin.
material_cost_per_kgNoBYO pricing: override material $/kg.
machine_rate_per_hourNoBYO pricing: machine time cost/hour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"BYO pricing: currency code (USD, EUR, ...). Default USD."New value: +"BYO pricing: currency code (USD, EUR, ...). Default USD. Only a label: amounts are NOT converted, so pass your own rates in that currency too."
    • changedInput schema / properties / minimum_price / description
      Previous value: -"BYO pricing: per-unit price floor."New value: +"BYO pricing: per-unit price floor, applied after volume discounts."
    • changedInput schema / properties / model_url / description
      Previous value: -"PREFERRED. 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."New value: +"PREFERRED. Public URL to the 3D model. Paste a link: 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). Thingiverse/Printables/MakerWorld pages usually block server downloads: download the file yourself and upload it. Local file? Upload once at https://fabtally.com/upload and paste that URL. The server fetches and (if a zip) unpacks it."
    • changedInput schema / properties / printer / description
      Previous value: -"Printer 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."New value: +"Printer id from list_printers (elegoo-centauri-carbon, 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-centauri-carbon."
    • changedInput schema / properties / setup_fee / description
      Previous value: -"BYO pricing: flat per-job setup fee."New value: +"BYO pricing: flat setup fee, charged once per job (not per part)."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the FREE/fair-use limit, that the server fetches and unpacks archives, that Thingiverse/Printables/MakerWorld block server downloads, and that large base64 arguments get silently truncated by MCP clients. It omits what the returned slice output looks like in any detail.

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

Conciseness3/5

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

The opening sentence is well front-loaded, but the following paragraph duplicates the model_url and model_base64 schema descriptions nearly word-for-word, which is length that does not earn its place. Still readable and scannable.

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?

For a 14-parameter tool with no output schema and no annotations, the description covers input sourcing, cost/pricing intent, and hints at the return (time/filament/cost). The BYO pricing parameters are left entirely to the schema, but that schema is fully described, so the gap is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including the BYO pricing fields is already documented. The link-handling paragraph in the description largely restates the model_url schema description verbatim, adding no meaning beyond structured data; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: recommend layer height/infill/walls for a goal and then slice with those settings to show time/filament/cost. This distinguishes it in substance from slice_model and cost_breakdown, though no sibling is named explicitly, so differentiation must be inferred.

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?

Gives concrete input routing: paste a public link, upload local files at the upload URL, or use base64 only for small files. It does not state when to prefer this tool over siblings like slice_model or optimize_orientation, but the input guidance is unusually specific.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources