Skip to main content
Glama

Export a 2D drawing

export_2d

Flatten the model to 2D as DXF or SVG, for a laser, vinyl cutter or CNC. The default "silhouette" projects it onto the view plane; "section" cuts through it — how to check an internal wall or bore no render shows.

Input Schema

NameRequiredDescriptionDefault
zNoSection position, mm, on the view axis (z, y or x).
cutNoSVG: hairline laser cut lines, no fill.
arcsNoDefault true: facets become true circles and arcs.
modeNoDefault "silhouette" (footprint). "section" needs `z`.
scadNoOpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses; BOSL2/MCAD includes resolve. minkowski() and resize() are not supported here — use hull() or offset().
viewNoDefault "top"; "front" from −y, "right" from +x.
nodesNoParametric node tree. mm, Z-up, rotations in DEGREES (a rotation.* binding: radians). Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong.
formatNoDXF for CAD/CAM and lasers, SVG for cutters and the web.dxf
deliverNoHow to return the bytes. `inline` (default) is base64 in the result, capped because it lands in your context. `url` writes the file to your account and returns a link good for 24 h instead, which lifts those caps — use it for anything large, or to hand a person a file.inline
projectIdNoId of one of your saved projects, as an alternative to `nodes`/`scad` (supply exactly one).
dxfVersionNoDXF flavour (default R2000; use R12 for older controllers).
smoothnessNoCurve quality for shapes that left their segment count automatic. Defaults to "standard", which is the editor default — pass "high" to match a project authored at high smoothness, "draft" for a cheaper check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / generatorKey / description
      Previous value: -"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."New value: +"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · bevelPair · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."
  2. Changed6 schema fields changed
    • addedInput schema / properties / arcs
      Added value: +{
      +  "description": "Default true: facets become true circles and arcs.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / cut
      Added value: +{
      +  "description": "SVG: hairline laser cut lines, no fill.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / format / description
      Previous value: -"File format: DXF for CAD/CAM and laser software, SVG for vinyl cutters and the web."New value: +"DXF for CAD/CAM and lasers, SVG for cutters and the web."
    • changedInput schema / properties / nodes / description
      Previous value: -"Parametric node tree. mm, Z-up, rotations in DEGREES. Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong."New value: +"Parametric node tree. mm, Z-up, rotations in DEGREES (a rotation.* binding: radians). Read owlcad://schema/primitives for every primitive, modifier and generator and its parameter ranges (unknown params are dropped silently), and owlcad://schema/conventions for the placement arithmetic, which is where most models go wrong."
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "Default \"top\"; \"front\" from −y, \"right\" from +x.",
      +  "enum": [
      +    "top",
      +    "front",
      +    "right"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / z / description
      Previous value: -"Slice height in mm (mode=section). The response reports the model’s z range when this misses it."New value: +"Section position, mm, on the view axis (z, y or x)."
  3. Changed1 schema field changed
    • changedInput schema / properties / nodes / items / properties / generatorKey / description
      Previous value: -"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap."New value: +"Generator to expand (kind=generator). PREFER one over hand-building the same thing — they carry standards dimensions and solve fits a tree of primitives gets subtly wrong: gearTrain · planetary · rackPinion · wormDrive · herringbone · herringboneTrain · pulley · bearing · belt · spring · adapter · boardMount · enclosure · gridfinity · threadedJar · pinHinge · snapFit · ballSocket · fastener · textPlate · fitCoupon · calibrationBlock · clamp · impeller · axialFan · fanFrame · plugCap · pillowBlock."
  4. Changed1 schema field changed
    • changedInput schema / properties / scad / description
      Previous value: -"OpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses. minkowski() and resize() are not supported here — use hull() or offset()."New value: +"OpenSCAD source, as an alternative to `nodes` (supply exactly one). Interpreted by the same engine the editor’s .scad import uses; BOSL2/MCAD includes resolve. minkowski() and resize() are not supported here — use hull() or offset()."
  5. Changed1 schema field changed
    • addedInput schema / properties / format / description
      Added value: +"File format: DXF for CAD/CAM and laser software, SVG for vinyl cutters and the web."
  6. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral context about what section mode reveals, but it does not disclose account file writing, inline size caps, or other export side effects covered only by schema parameters.

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?

Two sentences, front-loaded with the core action. Every clause earns its place by clarifying output formats, use cases, or mode behavior; no redundant restatement of the name or schema.

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 12-parameter export tool with a rich input schema and no output schema, the description adequately covers the core flattening behavior and the critical mode distinction. Details like model input selection and return delivery are left to the detailed schema, so the description is complete enough but not exhaustive.

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 description coverage is 100%, so the baseline is 3. The description adds interpretive meaning beyond the schema for mode (silhouette projects to the view plane; section cuts through for internal inspections) and implies format choice for different machines.

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 and resource: flatten the model to 2D as DXF or SVG. It clearly distinguishes itself from 3D export siblings like export_step by emphasizing 2D output formats and fabrication use cases.

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?

Gives clear context (laser, vinyl cutter, CNC) and explains the two mode choices: silhouette for projection, section for cutting through and checking hidden internal features. It does not explicitly compare itself to export or export_step, so it stops short of full alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources