Make Parts Now: 3D Printing & CNC Machining Quotes

upload_part

Upload a CAD file (STL, 3MF, OBJ, STEP) from an https URL or base64 content (filename required for base64). MCP requests are limited to 4 MB, so base64 works for files up to about 3 MB; use a URL or get_upload_url for larger files. no_controlled_data must be true: confirms the file has no CUI/ITAR/export-controlled data. Returns a part with status 'pending'; poll get_part until 'ready' (usually seconds), or pass wait_seconds.

Input Schema

Name	Required	Description
`url`	No	Public https URL of the CAD file; we fetch it server-side
`filename`	No	File name with extension (.stl, .3mf, .obj, .step); required with content_base64
`wait_seconds`	No	Seconds (0-30) to wait server-side for the analysis to finish before answering; 0 answers at once
`content_base64`	No	The file's bytes, base64-encoded (up to about 3 MB)
`idempotency_key`	No	Same key on a retry returns the first result instead of creating another
`no_controlled_data`	Yes	Must be true: confirms the file contains no CUI, ITAR, or export-controlled data

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "default": 0,
+  "description": "Seconds (0-30) to wait server-side for the analysis to finish before answering; 0 answers at once",
+  "maximum": 30,
+  "minimum": 0,
+  "title": "Wait Seconds",
+  "type": "integer"
+}

Changed1 schema field changedOct 10, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 255,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Same key on a retry returns the first result instead of creating another",
+  "title": "Idempotency Key"
+}

First observedOct 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare mutation/idempotency/open-world traits; the description adds operational constraints the annotations cannot convey: the 4 MB MCP request ceiling, the ~3 MB practical base64 limit, the mandatory no_controlled_data compliance gate, and the asynchronous 'pending' → 'ready' lifecycle.

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?

Four tight sentences, front-loaded with the action and accepted formats, then limits, then compliance, then return/polling behavior. No filler and no repetition of structured data.

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?

An output schema exists so return details needn't be spelled out, yet the description still notes the 'pending' status and polling path. Together with limits, compliance gating, and the large-file alternative, nothing needed to call this correctly is missing.

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 baseline is 3, but the description adds meaning beyond the schema: it ties filename to the base64 path, explains the base64 size ceiling, and states no_controlled_data must be true as a compliance assertion rather than just a flag.

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?

Opens with a specific verb and resource ('Upload a CAD file') and enumerates the accepted formats (STL, 3MF, OBJ, STEP) plus the two input channels (https URL or base64). This clearly separates it from siblings like get_upload_url and get_part.

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 routes the agent: base64 only works up to ~3 MB due to the 4 MB MCP request limit, so 'use a URL or get_upload_url for larger files'. It also names the follow-up action (poll get_part until 'ready', or use wait_seconds).

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

All Make Parts Now: 3D Printing & CNC Machining Quotes 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?