Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_preview_image

Read-only

Generate a PNG preview of the current BricsCAD drawing to visually verify work without changing the drawing.

Instructions

Return a PNG of the current drawing, to check work by eye. The drawing is not changed.

layout: "Model" or a sheet name. Defaults to the current layout. The whole layout is shown. window: [x1, y1, x2, y2] in drawing units, to show only that area. The image is the size of the BricsCAD window. The model shows on black, as on screen.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bricscad_preview_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutNo
windowNo
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The description asserts 'The drawing is not changed,' which matches readOnlyHint=true and destructiveHint=false, so there is no contradiction. It also adds useful visual context (the image is the size of the BricsCAD window, and the model shows on black), but it does not cover the timeout parameter's behavior or what happens on failure, so the additional disclosure is moderate rather than rich.

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 purpose is front-loaded in the first sentence, and the parameter notes follow in a readable list. Minor formatting noise (line breaks in the middle of sentences, a lowercase 'layout:') slightly hurts scanning, but no sentence is wasted.

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 read-only preview tool with no output schema and no required parameters, this is close to complete: it states the output format (PNG), the view scope, the default layout, the window semantics, and rendering context. The only gap is the undocumented timeout parameter.

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 0%, so the description must document all parameters. It explains layout well: 'Model' or a sheet name, defaulting to the current layout and showing the whole layout. It also documents window as [x1, y1, x2, y2] in drawing units. It explains two of the three parameters but says nothing about timeout.

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?

The description uses a specific verb and resource: 'Return a PNG of the current drawing, to check work by eye.' That clearly separates it from siblings such as bricscad_export_dxf or bricscad_plot_pdf, though it never names those siblings as alternatives.

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?

'to check work by eye' hints at when to call the tool (visual verification), but there is no explicit guidance on when to use this instead of bricscad_plot_pdf or bricscad_export_dxf, and no exclusions or prerequisites are stated.

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