Skip to main content
Glama

export_dxf

Exports a takeoff sheet as a real-unit DXF CAD drawing, placing committed shapes on finish-specific layers for import, layer isolation, and geometry audit.

Instructions

The takeoff as a CAD drawing — a DXF (R2000) AutoCAD, BricsCAD, LibreCAD and Revit import as native geometry, not a picture. ONE sheet per file, like a DWG: every committed shape on that sheet becomes an LWPOLYLINE (floor rings CLOSED, walls and linear runs open, count marks a 1-ft circle), on a layer named for its finish — OT-, with -DEDUCT / -HOLE / -WALL / -LINEAR / -COUNT suffix layers so a CAD user isolates any bucket with one layer filter, and room labels as TEXT on OT-LABELS. Coordinates are real units in the sheet's own frame: origin at the sheet's BOTTOM-left, Y up (CAD convention), feet by default ($INSUNITS 2) or metres with units:"m"; a ring's area in CAD equals its area in export_report to rounding, so the drawing IS the audit. Requires the sheet's scale (refuses otherwise — pixels in a DXF are worse than nothing); with several sheets carrying shapes, pass sheet to choose the drawing (the refusal lists them). The reply names every shape left out and why — a reconciled deduct ships as its parent's -HOLE ring, never twice. Writes to path (required — a DXF lives on disk, next to the DWG it aligns to); pair with export_marked_pdf for the reviewed planset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "export_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path to write the .dxf to
sheetNoSheet key ("plan.pdf", "plan.pdf#2") or title-block number ("A-101"). Optional only when exactly one calibrated sheet carries shapes
unitsNoOutput units — "ft" (default) or "m"
overwriteNoReplace the file at path even when it is not an OpenTakeoff export. Off by default: re-exporting over a previous export of your own already overwrites without this, so you only need it to deliberately destroy an unrelated file.

Output Schema

NameRequiredDescriptionDefault
pathYesThe DXF written
bytesYes
sheetYesSheet key the drawing was cut from
unitsYes
layersYesLayer names in table order — OT-<TAG>, plus -DEDUCT/-HOLE/-WALL/-LINEAR/-COUNT suffix layers and OT-LABELS
shapesYesCommitted shapes that produced geometry
extentsYesModel-space bounding box in output units; origin = sheet's bottom-left, Y up
skippedYesShapes on this sheet left out, each with why — never silent
entitiesYesLWPOLYLINE + CIRCLE + TEXT entities in model space
sheet_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.31
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / bytes / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / bytes / minimum
      Added value: +-9007199254740991
    • addedOutput schema / properties / entities / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / entities / minimum
      Added value: +-9007199254740991
    • changedOutput schema / properties / extents / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "max": {
      -        "items": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "number"
      -          }
      -        ],
      -        "maxItems": 2,
      -        "minItems": 2,
      -        "type": "array"
      -      },
      -      "min": {
      -        "items": [
      -          {
      -            "type": "number"
      -          },
      -          {
      -            "type": "number"
      -          }
      -        ],
      -        "maxItems": 2,
      -        "minItems": 2,
      -        "type": "array"
      -      }
      -    },
      -    "required": [
      -      "min",
      -      "max"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "max": {
      +        "additionalItems": false,
      +        "items": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "number"
      +          }
      +        ],
      +        "maxItems": 2,
      +        "minItems": 2,
      +        "type": "array"
      +      },
      +      "min": {
      +        "additionalItems": false,
      +        "items": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "number"
      +          }
      +        ],
      +        "maxItems": 2,
      +        "minItems": 2,
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "min",
      +      "max"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / shapes / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / shapes / minimum
      Added value: +-9007199254740991
  2. Addedv0.1.20

TDQS

A4.6/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 behavioral burden and does so thoroughly: it documents DXF format, one-sheet-per-file behavior, layer taxonomy, coordinate origin and Y-up convention, unit handling, scale refusal, sheet-selection refusal listing, and how reconciled deducts are represented. It also states that the reply names excluded shapes and why, which is important operational context.

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?

The description is dense and front-loads the core purpose before moving through geometry, units, sheet selection, exclusions, and output path. It is long but most sentences add useful operational detail, with only minor opportunities to tighten phrasing.

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?

Given a 4-parameter tool with an output schema, the description is complete enough for correct invocation. It covers the required output path, scale precondition, sheet disambiguation, units, layer semantics, and what happens to excluded or reconciled shapes without needing to repeat return-value details already captured by the output schema.

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 already 100%, so the baseline is 3, but the description adds useful meaning about units and sheet selection beyond the schema text. It clarifies that path is a real on-disk DXF target aligned to the DWG, and explains the default feet behavior versus metres with units:"m".

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 verb and resource: exporting the takeoff as a DXF CAD drawing. It clearly distinguishes this from a picture export and from sibling exporters like export_marked_pdf, and it explains the native-geometry output format.

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 gives explicit preconditions and routing guidance: the sheet must have a scale or the tool refuses, and with multiple shape-bearing sheets the caller should pass sheet. It also recommends pairing with export_marked_pdf for the reviewed planset, though it does not directly compare this tool to every other export sibling.

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