Skip to main content
Glama

OwlCAD

by com.owlcad.mcp
OverviewDiscussionsAdmin

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

TableJSON 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. 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)."
  2. 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."
  3. 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()."
  4. 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."
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds useful behavioral semantics about silhouette vs section geometry. It does not state side effects such as file creation or the fact that deliver=url writes to the account, which matters for a tool flagged non-read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the core action front-loaded ahead of the mode distinction. The trailing clause about internal walls/bore is somewhat awkwardly worded and slightly obscures its own point, costing a point.

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 tool the description correctly focuses on purpose and mode semantics while the fully-covered schema handles parameters and the three mutually exclusive input sources (nodes/scad/projectId). No output schema exists, so return values need not be described; remaining gaps are minor.

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 description coverage is 100% and every one of the 12 parameters carries its own prose, so the schema does the heavy lifting. The description reinforces mode semantics but adds little syntax or default information not already in the schema, matching the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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') and names the two generation modes and their meaning. It never names a sibling (export, export_step, import_2d), so the agent must infer the 2D vs 3D split from context, keeping this short of a 5.

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 concrete applicable contexts (laser, vinyl cutter, CNC) and routes between the two modes: default silhouette for footprint, section 'how to check an internal wall or bore no render shows'. It offers no explicit when-not or named alternative tool, so it is clear context without exclusions.

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

All OwlCAD toolsInspect
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