multiCAD-mcp-server

Overview Schema Source Related Servers Discussions Admin

export_data

Extract drawing measurements, quantity takeoffs, and budgets, then export to Excel, BC3, PDF, or JSON for documentation and cost estimation.

Instructions

Extract drawing measurements, bill of quantities, budget standards, or plot vector PDF sheets.

Behavior:

Mutation: Strictly read-only for drawing geometry; does not alter CAD entities or model database.
Persistence: When format is "excel", "bc3", or "pdf", writes persistent files to configured output directory.
Side Effects: Filesystem file creation/overwrite in output directory. If format="json", purely returns in-memory payload without disk writes.

Usage Guidelines:

When to Use: Call to extract structured quantity takeoffs, generate Excel spreadsheets (.xlsx), export Spanish AECO construction budgets (.bc3 FIEBDC-3), plot publication vector PDFs (.pdf), or retrieve JSON drawing entities.
Sibling Routing / Alternatives:
- For extracting thermal envelope parameters specifically formatted for energy certification in CE3X, use export_ce3x_envelope.
- For interactive browser visualization of the plan, use show_drawing_viewer.
- For spatial queries or bounding box summaries, use inspect_drawing.

Parameters:

scope: Entity selection scope ("all", "selected"). Default: "all".
- "all": Processes all entities across visible layers.
- "selected": Restricts export to currently selected entities in CAD viewport.
format: Output serialization format ("json", "excel", "bc3", "pdf"). Default: "json".
- "json": Returns parsed entity array directly to LLM context.
- "excel": Generates multi-tab Excel workbook with layer summaries, lengths, and areas.
- "bc3": Generates standard FIEBDC-3/2020 budget and measurement exchange file.
- "pdf": Plots modelspace/paperspace to standard vector PDF 1.4 document.
filename: Output file name or relative path (e.g. "mediciones.xlsx", "presupuesto.bc3", "plano.pdf").
paper_size: Paper standard when format="pdf" ("A4", "A3", "A2", "A1", "A0"). Default: "A3".

Returns: JSON string containing export summary, file path, exported entity counts, or extracted entity data.

Input Schema

TableJSON Schema

Name	Required	Default
`scope`	No	all
`format`	No	json
`filename`	No	drawing_data.xlsx
`paper_size`	No	A3

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.9/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 burden and does so: it states read-only-ness for geometry, that excel/bc3/pdf formats write persistent files to the output directory, that files may be created/overwritten, and that json is purely in-memory. This is exactly the safety and side-effect context an agent needs before invoking.

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?

Heavily structured with labeled sections and front-loaded, but somewhat verbose: the Returns section is redundant with the existing output schema and the mutation/persistence/side-effects bullets could be tightened. Still, nearly every line earns its place for a 4-parameter, no-annotation tool.

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 mutation-capable export tool with no annotations and a 0%-covered schema, the description covers purpose, routing, side effects, per-parameter semantics, and return shape. An agent has everything required to call it correctly; the output schema further covers return structure.

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?

Schema description coverage is 0%, so the description must compensate, and it does: every parameter (scope, format, filename, paper_size) is explained with its allowed values, defaults, and per-value behavior (e.g. what each format produces, pdf paper standards). It adds substantial meaning beyond the bare property names in the schema.

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 opens with a specific verb and enumerates the concrete resources extracted (drawing measurements, bill of quantities, budget standards, vector PDF sheets), and explicitly names sibling tools it is not (export_ce3x_envelope, show_drawing_viewer, inspect_drawing). An agent can disambiguate without reading any schema.

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

Usage Guidelines5/5

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

It provides an explicit 'When to Use' section plus a 'Sibling Routing / Alternatives' list naming three alternatives with the exact condition that selects each (CE3X energy certification, browser visualization, spatial queries). Nothing is left to inference.

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

Deploy Server