Skip to main content
Glama

export_dxf

Export takeoff quantities as a DXF CAD drawing. The file uses real units, layer-separated shapes, and room labels, making it ready for CAD workflows.

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.

Input Schema

TableJSON 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

TableJSON 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. Dates show when Glama detected each change.

  1. Addedv0.1.20

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and succeeds thoroughly. It discloses output geometry, layer naming, coordinate conventions, units, scale requirements, refusal behavior, handling of missing shapes, and overwrite semantics — far beyond what an annotation could capture.

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 front-loaded with the core purpose, and every sentence adds technical or behavioral value. It is dense and somewhat run-on, but for a CAD export tool with many edge cases, the length is justified. It could be tightened with clearer sentence breaks.

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 the tool's complexity, the description covers all essential operational concerns: output format, layer organization, coordinate system, units, scale prerequisite, multi-sheet selection, exclusions, overwrite safety, and a companion PDF tool. The presence of an output schema means return-value details are not needed here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaningful meaning: path is required because DXF is a disk file aligned to the DWG; sheet is optional only when one calibrated sheet carries shapes; units affect INSUNITS; and overwrite has a nuanced 'your own previous exports already overwrite' behavior. This is more than baseline schema documentation.

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 the tool exports the takeoff as a CAD drawing in DXF R2000 format, with native geometry rather than an image. It clearly distinguishes this from export_marked_pdf by emphasizing CAD interoperability and from export_report by noting that CAD areas match the report's areas.

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 provides strong context: requires a calibrated sheet scale, requires a path, and explains when to pass the sheet parameter. It also names export_marked_pdf as a companion for a reviewed planset. However, it never explicitly states 'use this instead of X when Y' or lists exclusion conditions beyond the scale requirement.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kentucky-ai/opentakeoff'

If you have feedback or need assistance with the MCP directory API, please join our Discord server