Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_erase_entities

Destructive

Erases drawing entities by handle in BricsCAD, applying the operation to all listed handles or none. It skips entities on locked layers and block-owned attributes.

Instructions

Erase entities by handle. Erases all of them or none. bricscad_undo restores them.

Refuses entities on locked layers and attributes, which belong to their block insert.

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": {
      "handles": "<handles>"
    },
    "name": "bricscad_erase_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
handlesYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the risk profile is covered. The description still adds real value with atomicity ('all of them or none'), undo-based reversibility, and the two refusal classes. It says nothing about side effects on dependent geometry (hatches, dimensions) or what the response reports when the batch is refused, so it is good but not exhaustive 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.

Conciseness4/5

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

Three short sentences, front-loaded with the action, then the atomicity contract, then refusal rules. The trailing clause 'which belong to their block insert' is compressed to the point of being slightly ambiguous, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 destructive semantics are covered. However, for a batch destructive mutation with 0% schema coverage, the missing handle format and timeout meaning leave an agent without enough information to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter burden. It clarifies that handles are accepted and are all-or-nothing, but never gives the handle format (hex string, entity ID?) and never mentions the second parameter, timeout, at all. Half the parameters remain undocumented anywhere.

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 ('Erase entities') plus the identification mechanism ('by handle'), which separates it from create/modify/query siblings by implication. It stops short of explicitly contrasting with bricscad_modify_entities, but an agent can still tell what this tool does.

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 concrete preconditions for when the tool will not act (locked layers, attributes owned by a block insert) and names bricscad_undo as the recovery path. It does not explicitly say when to prefer modify_entities or set_layer over erasing, leaving that choice to inference.

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