import_surface_attachment

Import an already attached STL/STEP/STP/3MF using the actual file reference supplied by the chat host.

Scope: artifacts:write. Catalogue annotation: Writes / prepares / submits work. Additional ownership and role checks may apply.

REST: POST /v1/artifacts/attachment-imports.

Arguments

Field

Type / accepted values

Required

Default

Constraints / meaning

coordinate_units

"auto" / "mm" / "cm" / "m" / "in"

No

"auto"

Normally auto. STEP/STP/3MF use embedded units normalized to mm. STL units are resolved from measured bounds and supplied engineering context; ambiguous scale requires one clarification.

engineering_context

string or null

No

null

maxLength: 1000; Brief supplied engineering context, e.g. a full-size passenger car or a GPU cold plate. Do not infer context from a filename alone.

expected_length_mm

number or null

No

null

maximum: 1000000000.0; exclusiveMinimum: 0; Optional known approximate longest overall dimension in millimetres. Supply only when known from the user or source evidence, not an invented guess.

project_id

string (uuid) or null

No

null

request_id

string (uuid) or null

No

null

filename

string

Yes

Omitted

minLength: 1; maxLength: 180

size_bytes

integer or null

No

null

maximum: 5000000000; exclusiveMinimum: 0

sha256

string or null

No

null

pattern: "^[a-f0-9]{64}$"

file

ChatAttachment

Yes

Omitted

Calling the tool

Use tools/call with this tool’s exact name and an arguments object matching the fields above. Get the complete live schema before supplying advanced controls:

{
  "name": "get_tool_schema",
  "arguments": {
    "name": "import_surface_attachment",
    "include_definitions": false
  }
}

Result and continuation

Inspect isError and structuredContent. Keep returned job, operation and artifact IDs. A pending operation_id is followed with get_operation; a compute job is followed with get_job. A wait timeout does not cancel work. Follow returned polling intervals and retain the same idempotency key when reconciling the same submission.

See agent workflow, jobs and operations, uploads, results and error recovery for the applicable lifecycle. MCP annotations describe tool behaviour; they are not blanket permission to run paid work or change account state.