Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_stop

Destructive

Closes the BricsCAD instance started by the server and blocks shutdown when drawings have unsaved changes; set discard to true to close anyway and lose those changes.

Instructions

Close the BricsCAD this server started. Refuses if drawings have 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_stop"
  }
}

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, and the description earns credit by specifying exactly what happens: it refuses when unsaved changes exist, and discard=true destroys them. That is concrete disclosure of consequence and failure mode beyond 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.

Conciseness5/5

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

Two short sentences, front-loaded with the default-safe behavior before the override. Every clause adds information; nothing is redundant.

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 values need no explanation, and the safety-critical behavior is fully covered. Minor residual gaps are whether it kills the process or waits, and what happens to open-but-saved drawings, but nothing essential to a correct call is missing.

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 description coverage is 0%, so the description carries the full burden for the single parameter, and it does: discard=true overrides the refusal and loses unsaved changes. This gives the agent both the meaning and the risk of the flag.

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 BricsCAD this server started") and scopes it to the server-launched instance, which implicitly separates it from bricscad_close_drawing. It does not explicitly name that sibling or say it applies to the application rather than a document, so it falls just short of a 5.

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?

The refusal-on-unsaved-changes rule tells the agent when the call will fail and what condition selects the discard path, which is useful context. However, no alternative tools (e.g. saving first, closing a drawing) are named, so guidance 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.