Skip to main content
Glama

HardCopy Labs

by com.hardcopylabs
OverviewDiscussionsAdmin

Check a 3D model and get a price

validate_stl
Read-onlyIdempotent

Check whether a 3D model can be printed, before ordering.

A text validation quote is NOT approval to order. Call preview_print_order next,
show its exact model images/options/price to the buyer, then obtain confirmation.

Use this when the user has an STL file (base64-encoded) and wants to know if it
is printable, or as a pre-check before submit_print_job. Returns printability
(watertight/manifold status), dimensions, which printers it fits on, and the
total for each material: what submit_print_job will charge for this file,
shipping included. If the user is designing an object in this conversation, generate the
STL, then call this to confirm it can be manufactured. Pass quantity (default 1) when
the user wants several copies, so the totals cover all of them.
For multiple parts, pass the WHOLE order in parts with each material/color/quantity.
Never add separate quotes: totals already include shipping and handling once.
To keep payloads small, validate each STL first and reuse its model_id (24 hours).
PLA and PETG are the only materials offered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partsNoThe WHOLE order, one entry per part. Use a model_id from earlier validation, an STL, or OpenSCAD. Each entry has its own name, material, color and quantity. Each part's quantity is capped by its own print time, not a flat count. Shipping and handling are charged once; never add independent quote totals.
quantityNoHow many identical copies. The totals cover all of them. Capped by how long the part takes to print, not a flat number -- a quick part allows many copies, a very large or slow one may allow as few as 1; submit_print_job reports the real cap if this is too many.
stl_base64NoThe model as a base64-encoded STL file (binary or ASCII), in millimeters.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $defs
      Added value: +{
+  "OrderPart": {
+    "additionalProperties": false,
+    "properties": {
+      "color": {
+        "default": "black",
+        "description": "Filament color for this part.",
+        "maxLength": 40,
+        "title": "Color",
+        "type": "string"
+      },
+      "material": {
+        "default": "pla",
+        "description": "PLA or PETG only.",
+        "maxLength": 20,
+        "title": "Material",
+        "type": "string"
+      },
+      "model_id": {
+        "default": "",
+        "description": "Reusable id from validate_stl; valid for 24 hours.",
+        "maxLength": 64,
+        "title": "Model Id",
+        "type": "string"
+      },
+      "name": {
+        "description": "Short part name, shown on the card and receipt.",
+        "maxLength": 120,
+        "minLength": 1,
+        "title": "Name",
+        "type": "string"
+      },
+      "openscad_source": {
+        "default": "",
+        "description": "OpenSCAD in millimeters; give exactly one model source.",
+        "maxLength": 50000,
+        "title": "Openscad Source",
+        "type": "string"
+      },
+      "quantity": {
+        "default": 1,
+        "description": "Copies of THIS part. Capped by how long this part takes to print, not a flat number -- checked once its geometry is known; a rejected order reports the real cap for this part's size.",
+        "maximum": 500,
+        "minimum": 1,
+        "title": "Quantity",
+        "type": "integer"
+      },
+      "stl_base64": {
+        "default": "",
+        "description": "STL in millimeters; give exactly one model source.",
+        "maxLength": 25000000,
+        "title": "Stl Base64",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "title": "OrderPart",
+    "type": "object"
+  }
+}
    • addedInput schema / properties / parts
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/OrderPart"
+      },
+      "maxItems": 20,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The WHOLE order, one entry per part. Use a model_id from earlier validation, an STL, or OpenSCAD. Each entry has its own name, material, color and quantity. Each part's quantity is capped by its own print time, not a flat count. Shipping and handling are charged once; never add independent quote totals.",
+  "title": "Parts"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -"How many identical copies, 1 to 20. The totals cover all of them."New value: +"How many identical copies. The totals cover all of them. Capped by how long the part takes to print, not a flat number -- a quick part allows many copies, a very large or slow one may allow as few as 1; submit_print_job reports the real cap if this is too many."
    • addedInput schema / properties / stl_base64 / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "stl_base64"
-]
  2. Changed2 schema fields changed
    • addedInput schema / properties / quantity
      Added value: +{
+  "default": 1,
+  "description": "How many identical copies, 1 to 20. The totals cover all of them.",
+  "title": "Quantity",
+  "type": "integer"
+}
    • addedInput schema / properties / stl_base64 / description
      Added value: +"The model as a base64-encoded STL file (binary or ASCII), in millimeters."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial non-obvious behavior: the quote is not order approval, buyer confirmation is required via preview_print_order, model_id is reusable for 24 hours, totals already include shipping/handling and must not be added separately, and only PLA/PETG are offered. This is real workflow context beyond the structured fields.

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 critical constraint (quote is not approval) is front-loaded, and the remaining sentences are directive rather than filler. It runs a bit long and some workflow guidance could be tightened, but nothing is redundant bloat.

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?

With an output schema present, the description need not explain return values, yet it still names what matters (printability, dimensions, printer fit, per-material totals that match submit_print_job). Combined with the workflow routing, an agent has everything needed to call and sequence this tool correctly.

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 the baseline is 3, but the description adds meaning: quantity defaults to 1 and drives totals ('pass quantity when the user wants several copies, so the totals cover all of them'), and multi-part orders must be passed whole in parts. It clarifies intent and aggregation semantics rather than repeating field definitions.

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?

States a specific verb+resource: validating an STL's printability and returning a price total per material. It clearly distinguishes itself from submit_print_job (the actual order) and preview_print_order (the confirmation step), so an agent can place it in the workflow without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('when the user has an STL file and wants to know if it is printable', 'pre-check before submit_print_job'), an explicit next-step ('Call preview_print_order next... then obtain confirmation'), and an exclusion ('A text validation quote is NOT approval to order'). Routing is unambiguous.

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

All HardCopy Labs 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