Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_close_drawing

Destructive

Close the current drawing while protecting unsaved changes; set discard to true to force closure and lose any edits.

Instructions

Close the current drawing. Refuses if it has unsaved changes.

discard: true closes it anyway and loses the unsaved changes.

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

Input Schema

NameRequiredDescriptionDefault
discardNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds real information beyond them: the precondition under which the call fails and exactly what is lost when discard is set. It does not describe what the tool returns on success or failure, which keeps it out of the top band.

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?

Three short sentences: purpose first, the refusal condition second, the parameter escape hatch third. No filler, and the destructive consequence is front-loaded rather than buried.

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 simple one-parameter mutation tool with an output schema, so return values need no explanation here. The definition covers the precondition, the destructive option, and the data-loss risk; the only minor omission is what happens when the close fails for reasons other than unsaved changes.

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 coverage is 0% — the single parameter has no description, only a default of false. The description fully compensates by explaining that discard:true bypasses the safety refusal and knowingly loses unsaved changes, which is precisely the meaning an agent needs.

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 ("Close the current drawing"), which is unambiguous and clearly distinct from save/open/info siblings. It does not explicitly name or contrast a sibling, so it lands just below the top band.

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 a conditional decision rule: if the drawing is dirty the call is refused, and discard:true overrides that but destroys changes. It stops short of naming the alternative path (e.g., save_drawing first), so usage guidance is implied rather than spelled out.

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