Skip to main content
Glama

Craft Quantities: construction material calculators

Export a drawing as DXF, SVG or IFC (CAD and BIM files)

export_drawing
Read-onlyIdempotent

Exports a Construction Canvas drawing (a template, shapes, a room layout, drawing commands, house figures or a canvas document) as DXF for CAD, with the site's CQ-* layers, and as SVG, one plan per level in millimetres, or as one openBIM IFC4 model with quantity sets, as the canvas's own download writes them; a file too large to return is rebuilt from the drawing's link.

Input Schema

NameRequiredDescriptionDefault
houseNoThe House Estimator's form: the house drawn as the estimator draws it.
levelNoOne level by its id or name; left out, every level with something on its plan.
detailNofull (the default): the whole answer. summary: the result lines, the citation line and the page only — fewer tokens to read.full
layoutNoRooms by name, size and which room each stands against, laid out on a grid: shared walls drawn once as partitions, every snap or move reported, and each room checked to close.
shapesNoSimple shapes the assistant has read from the reader's words — a room, a deck, a patio, a bed, a path, a fence of legs and turns — compiled into the canvas's own commands. Every length with its unit.
systemNoThe unit system inputs left out open in, and the one the page link opens in. The answer comes in both.metric
formatsNodxf, svg, ifc (openBIM IFC4: one file for the whole drawing, every level, with quantity sets), or several; left out, dxf and svg.
variantNoWith template: one of its two "what changes if" variants, by id; a wrong one is refused with the template's own list.
commandsNoDrawing commands, in order, on the canvas's blank drawing (one storey; the wall, partition, window and door types). The whole request is at most 64 KiB.
documentNoA Construction Canvas document (schema 1 to the canvas's current), opened and checked by the canvas's own opener.
templateNoA Construction Canvas template's slug (the template index lists them: single-room, deck, two-car-garage …): the drawing its page shows, in the reader's system, with a link that opens it.
inputUnitsNoSend "base" to pass bare numbers on dimensioned inputs in base units (m, m², L, kg …), as the published test vectors are written. Without it a length, area or volume must carry its unit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description usefully adds fidelity behavior ("as the canvas's own download writes them"), the DXF CQ-* layer convention, SVG being one plan per level in millimetres, IFC4 quantity sets, and the large-file fallback ("a file too large to return is rebuilt from the drawing's link"). Meaningful behavioral context beyond structured fields.

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?

A single front-loaded sentence that leads with the verb and resource; nearly every clause earns its place by adding a distinct output detail. It is slightly run-on with multiple semicolon-joined ideas, but there is no filler.

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 with full schema coverage, an output schema, and rich annotations, the description supplies the extra output-format and fallback context an agent needs. The main gap is routing advice among the many sibling tools, which keeps it from being fully complete.

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%, so all 12 parameters are already documented in the schema, which is the baseline for a 3. The description restates the format families (dxf/svg/ifc) and input sources but adds no syntax or constraints beyond what the schema already carries.

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 ("Exports a Construction Canvas drawing") and enumerates the accepted drawing sources (template, shapes, layout, commands, house figures, document) plus the three output formats, so its job is unambiguous. It stops short of naming how it differs from siblings like create_project_file_from_drawing, but the format-level detail is distinctive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says what it produces but never states when to reach for it over alternatives (e.g. create_project_file_from_drawing or open_in_site_link). The list of input sources implies what can be passed, but there are no conditions, prerequisites, or exclusions to guide selection.

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