Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_set_layer

Destructive

Create a new drawing layer or modify an existing one by setting its name, color, linetype, visibility, freeze, and lock state; only supplied properties change.

Instructions

Create a layer, or change one that exists. Only the values you give are changed.

new_name: rename the layer. Layers 0 and Defpoints cannot be renamed. color: a color number from 1 to 255. linetype: loaded from iso.lin if the drawing does not have it yet. on, frozen, locked: true or false. The current layer cannot be frozen.

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

Input Schema

NameRequiredDescriptionDefault
onNo
nameYes
colorNo
frozenNo
lockedNo
timeoutNo
linetypeNo
new_nameNo

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?

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses real behavioral traits: partial-update semantics, the un-renameable Layers 0/Defpoints, the un-freezable current layer, and the side effect of loading iso.lin when the linetype is missing. It omits what happens on invalid input or against a locked layer, and does not soften the destructiveHint framing for what is largely a settings edit.

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?

Core behavior is front-loaded in the opening sentence, followed by tight one-line-per-parameter notes with zero filler. Every line adds either a constraint or a parameter fact.

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?

With an output schema present, return values need no explanation, and the description covers the mutation semantics and most parameters. The remaining gap is the undocumented 'timeout' parameter and failure behavior, which matters modestly for a destructive-flagged write tool with 8 parameters.

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?

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does: color range 1-255, new_name renaming with its exceptions, linetype sourcing, and on/frozen/locked as booleans with a constraint on frozen. Only 'timeout' (and the role of 'name' as the lookup key) goes unmentioned, which keeps it below 5.

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 first sentence gives a specific verb+resource with upsert semantics: 'Create a layer, or change one that exists.' That clearly separates it from read-side siblings like bricscad_list_layers. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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?

'Create a layer, or change one that exists' plus 'Only the values you give are changed' tells the agent it does not need to probe for existence first and that partial updates are safe. No alternatives or when-not conditions are named, so it is clear context without exclusions.

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