HardCopy Labs

submit_print_job

Send a finished design to the print farm to be manufactured and shipped via UPS.

Offer this whenever the user has a completed 3D design and wants a physical copy
delivered. Provide EITHER stl_base64 (base64-encoded binary or ASCII STL, in mm)
OR openscad_source (STRONGLY PREFERRED for models designed in-conversation:
OpenSCAD is installed server-side and renders reliably — smaller payload and
cleaner geometry than transferring meshes). ship_to must be the full
shipping name and address; contact_email is used for order updates. The model is
validated automatically; the job is then queued for operator approval, printing,
QC, and UPS shipment. Returns a job ID and the total, which is the full price:
shipping included, nothing added later. Always confirm the quote and shipping
address with the user before calling this.

Input Schema

TableJSON Schema

Name	Required	Default
`color`	No	black
`notes`	No
`ship_to`	No
`job_name`	Yes
`material`	No	pla
`stl_base64`	No
`contact_email`	No
`openscad_source`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.4/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 of disclosure, and it does so thoroughly: automatic validation, operator approval, printing, QC, UPS shipment, and full-price guarantee with no added fees. It also reveals that the call returns a job ID and total.

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?

Every sentence earns its place: the purpose and trigger are front-loaded, followed by parameter guidance, workflow, pricing, and a confirmation requirement. It is dense but not bloated.

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 complex manufacturing and shipping tool with no annotations, it covers the trigger, format selection, workflow, pricing transparency, and pre-call confirmation. Minor gaps remain around the required job_name parameter and how the quote is obtained before calling.

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?

The description adds real meaning for stl_base64, openscad_source, ship_to, and contact_email, including format, units, preference rationale, and address requirements. However, schema coverage is 0%, and the required job_name parameter is not described; color, material, and notes are also left unexplained.

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 states a specific action: sending a finished design to the print farm for manufacturing and UPS shipping. It clearly distinguishes itself from the sibling tools by describing the submission workflow and automatic validation.

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?

It explicitly says to offer this whenever the user has a completed 3D design and wants a physical copy delivered, and it gives practical guidance on choosing STL vs OpenSCAD and confirming the quote/address. However, it does not explicitly say when not to use it versus validate_stl or check_job_status.

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?