Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_export_dxf

Destructive

Exports the active drawing to a DXF file at a specified path, preserving its name and state, with selectable DXF version and safe overwrite handling.

Instructions

Write the current drawing as a DXF file. The drawing keeps its name and state.

path: a .dxf file in an existing folder. It cannot be an open drawing. version: DXF version, R12 or 2000 to 2018. overwrite: true allows replacing an existing file. It is replaced only once the new one is complete.

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": "bricscad_export_dxf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
timeoutNo
versionNo2018
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds meaningful context beyond them: the source drawing is left unchanged, and with overwrite=true the existing file is replaced only after the new one is complete. That atomic-replacement note is valuable for an agent weighing the destructive flag. It does not mention timeout behavior or failure modes.

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 core action and its non-side-effect guarantee are front-loaded, then per-parameter notes follow compactly with no filler. Slightly list-like structure, but every line conveys information an agent needs.

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?

An output schema exists, so return-value description is unnecessary, and annotations cover the safety profile. What remains is nearly complete for a mutation/export tool, with the only real gap being the undocumented timeout parameter and no note on error behavior when the target path is unwritable.

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 description coverage is 0%, so the description carries the burden, and it documents three of four parameters with real constraints: path validity rules and overwrite semantics beyond the boolean default. The version range 'R12 or 2000 to 2018' restates the enum, and the timeout parameter is never mentioned.

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: 'Write the current drawing as a DXF file,' and adds scope with 'The drawing keeps its name and state,' which distinguishes it from a save operation. It does not name or contrast with any sibling such as bricscad_save_drawing, so it stops short of explicit differentiation.

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

Usage Guidelines3/5

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

Provides real preconditions: the path must be a .dxf in an existing folder and cannot be an open drawing. However, it never states when to choose this over bricscad_save_drawing or bricscad_plot_pdf, so the when-to-use routing is implied rather than explicit.

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