Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_save_drawing

Destructive

Save the current BricsCAD drawing to its open file or a new .dwg path, optionally overwriting existing files, and return updated drawing details.

Instructions

Save the current drawing. Returns the same details as bricscad_drawing_info.

path: a new .dwg path. The drawing then continues under that name, and is no longer read-only. Leave it out to save over the open file, which needs overwrite=true. overwrite: true allows replacing an existing file. BricsCAD leaves a .bak beside it. A read-only drawing cannot be saved over its own file, and a file open as another drawing cannot be replaced.

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_save_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
timeoutNo
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds substantial context beyond them: saving under a new path makes the drawing continue under that name and drop read-only status, overwriting leaves a .bak file beside the target, and certain read-only/duplicate-open cases are blocked. These are concrete side effects an agent could not infer from the annotations.

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?

Front-loads the purpose, then documents the consequential parameters, with almost no wasted wording. The prose is slightly fragmented by line breaks mid-sentence and the param labels are informal, but readability and density are good.

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?

A destructive write tool with annotations, an output schema (so return values need not be described, and it defers to bricscad_drawing_info anyway), and three parameters. Coverage of the risky parameters and failure conditions is strong; only the timeout parameter and any errors other than the two stated blocks are unaddressed.

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?

With 0% schema description coverage, the description carries the burden and explains path (creates new file, changes working name, clears read-only) and overwrite (permits replacing an existing file, produces a .bak) in useful detail. The third parameter, timeout, gets no mention, leaving a small but real gap.

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 ('Save the current drawing') and adds that it returns the same details as bricscad_drawing_info, which pins down both action and result shape. An agent can distinguish it from bricscad_close_drawing or bricscad_drawing_info from this sentence alone.

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?

Gives clear conditional guidance: omit path to save over the open file (requires overwrite=true), supply path to save-as under a new name. It also states two exclusion conditions — read-only drawings cannot be saved over their own file, and a file open as another drawing cannot be replaced. It does not name sibling alternatives, but the when/when-not conditions are explicit.

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