Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_plot_pdf

Destructive

Plot a BricsCAD layout or Model space to a PDF without altering the drawing; specify paper, orientation, area, scale, and plot style as needed.

Instructions

Plot one layout of the current drawing to a PDF file, with Print As PDF.pc3. The drawing is not changed.

path: a .pdf file in an existing folder. layout: "Model" or a sheet name. Defaults to the current layout. paper: BricsCAD's paper name, such as "ISO A3 (297.00 x 420.00 MM)". Defaults to the layout's current size. landscape: true or false. Defaults to the layout's current orientation. area: "extents", "layout" (sheets only) or "window". Defaults to extents for the model and layout for sheets. window: [x1, y1, x2, y2] in drawing units, with area="window". scale: "fit", or plotted millimetres to drawing units such as "1:100". Defaults to fit for the model and 1:1 for sheets. style_table: a plot style table such as "monochrome.ctb". Defaults to the layout's own. 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_plot_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
pathYes
paperNo
scaleNo
layoutNo
windowNo
timeoutNo
landscapeNo
overwriteNo
style_tableNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description usefully redirects that risk to the right place: the drawing itself is not modified, the destruction is limited to file replacement, and 'It is replaced only once the new one is complete' discloses atomic-write semantics. That is real behavioral context an agent cannot get from the annotations. Minor gap: no mention of permissions, failure modes, or that an existing file blocks the write when overwrite is false (only implied).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences establish purpose and the non-destructive guarantee, then a tight one-line-per-parameter list. No filler, no repetition of the tool name, and each line carries a distinct piece of information.

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?

For a 10-parameter, zero-schema-coverage tool this is close to complete: every semantically meaningful parameter has a format and default, and the overwrite/atomicity behavior is spelled out. Return values need not be described because an output schema exists, so the remaining 'timeout' omission is minor.

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% across 10 parameters, so the description must carry the full burden and largely does: it documents formats and defaults for path, layout, paper, landscape, area, window tuple layout in drawing units, scale syntax, style_table and overwrite. Only 'timeout' is left undocumented, which keeps it off a 5.

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?

States a specific verb and resource ('Plot one layout of the current drawing to a PDF file'), names the plot device configuration used, and adds a scoping fact ('The drawing is not changed') that separates it from sibling mutation tools like bricscad_create_entities or bricscad_save_drawing.

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?

Usage context is clear from the per-parameter defaults: it explains that layout defaults to the current layout, area defaults differently for model vs sheets, and scale defaults to fit/1:1 accordingly, which effectively tells an agent when the defaults suffice. It does not name an alternative tool (e.g. raster preview) or state exclusions, so it stops short of explicit when-not guidance.

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