HardCopy Labs

Preview the exact parts before ordering

preview_print_order

Read-onlyIdempotent

MANDATORY before creating any order or checkout, including reorders.

Render exact validated geometry and quote the whole order. Display EVERY returned
part image with name, dimensions, material/color, quantity, notes and total to the
buyer. The in-chat card shows images where supported; otherwise embed image_url
values or give viewer_url and ask the buyer to review there. Never substitute an
AI illustration, or describe unshown images as reviewed. Ask for explicit buyer
confirmation of this version only after presenting the preview. Changes require
a new preview and new confirmation; pass replaces_preview_id to revoke the old preview. Preview failure blocks ordering.

After confirmation call submit_print_job (or reorder_print_job) using preview_id,
preview_version, buyer_confirmed=true and shipping/contact details; do not resend
models or option overrides. Preview generation and viewing never create an order.
Separate parts are displayed individually, not as an inferred assembly.

Input Schema

TableJSON Schema

Name	Required	Description
`color`	No	Selected filament color. Default black for new models; omit to retain reorder colors.
`notes`	No	Operator instructions to show and bind to this preview; changes require a new preview.
`parts`	No	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.
`job_name`	No	Short order name shown with the preview.
`material`	No	PLA or PETG. Default PLA for new models; omit to retain reorder materials.
`quantity`	No	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.
`reorder_of`	No	Existing order ID to preview for reorder; omit new model inputs when using this.
`stl_base64`	No	The model as a base64-encoded STL file (binary or ASCII), in millimeters.
`openscad_source`	No	OpenSCAD source in millimeters. Rendered and validated before preview; never an illustrative AI image.
`replaces_preview_id`	No	When revising an unplaced order, pass its previous preview id. It is invalidated even if the new render fails.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 30, 2026

TDQS

A3.9/5.0

Behavior1/5

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

Annotations declare readOnlyHint=true, but the description says replaces_preview_id revokes the old preview and that it is invalidated even if the new render fails. This write/invalidation behavior contradicts the read-only annotation. The description adds rich workflow context, but the contradiction forces a score of 1.

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 long but front-loads the mandatory ordering constraint and then structures the workflow, display rules, confirmation requirement, and follow-up call clearly. Every sentence is relevant to correct invocation.

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 that an output schema exists and schema coverage is 100%, the description still supplies essential workflow context: failure blocking, buyer confirmation, image display behavior, and routing to submit/reorder tools. It is complete for a complex preview step.

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 coverage is 100%, and the schema already documents all 10 parameters in detail. The description adds workflow semantics such as not resending models and displaying separate parts individually, but it does not add much parameter-specific meaning beyond the schema. Baseline 3 is appropriate.

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 action: render validated geometry, quote the whole order, and display every returned part image with details. It distinguishes itself from submit/reorder by being mandatory before ordering. The verb and resource are clear.

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?

Explicitly says it is mandatory before creating any order or checkout, including reorders. It names the follow-up alternatives submit_print_job and reorder_print_job and gives the exact conditions and fields for using them. It also states that changes require a new preview and that preview failure blocks ordering.

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

All HardCopy Labs tools Inspect

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

Need Help?