Skip to main content
Glama

FabTally 3D-Print Slicer, Quote & DFM

Cost breakdown (material vs machine vs setup)

cost_breakdown

FREE. Break a quote into material vs machine-time vs setup vs margin, in your currency and filament price (bring your own pricing). 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 (one slice).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
qualityNoQuality preset: draft 0.28mm | standard 0.20mm | fine 0.12mm layer height.
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.
infill_percentNoSparse infill density percent (0-100).
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

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares FREE, fair-use limits (one slice), that the server fetches and unpacks archives, that some hosts block server downloads, and that inline base64 can silently corrupt. It omits auth requirements and any rate-limit specifics beyond 'fair-use'.

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?

Front-loads the purpose and 'FREE' well, but the entire 'Paste a link... download the file yourself... paste that URL' passage repeats the model_url schema description verbatim, adding length without new information. The margin/setup/currency framing sentence is a tighter, more useful summary.

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 15-parameter, no-output-schema tool, the description names the four output components (material, machine-time, setup, margin) and covers input sourcing fallbacks, which is enough for correct invocation. Only auth/rate-limit expectations and the returned shape of the breakdown remain unstated.

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 the schema already documents all 15 parameters including BYO pricing fields, enum values, and defaults. The description's URL guidance duplicates the model_url description almost verbatim and adds no new parameter semantics, so 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: 'Break a quote into material vs machine-time vs setup vs margin', which tells an agent exactly what output it produces. It does not name or differentiate against the closest sibling, get_print_quote, so an agent must infer the split between quoting and breaking down an existing quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance despite 13 siblings, including get_print_quote and compare_printers. The only context ('FREE', 'Fair-use limited (one slice)') is a constraint, not a selection criterion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.