Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_set_attributes

Destructive

Set attribute values on BricsCAD block inserts such as title blocks by handle and tag; retrieve handles and tags with bricscad_read_attributes to apply updates atomically.

Instructions

Set attribute values on block inserts, such as a title block. Changes all of them or none.

updates: [{"handle": insert handle, "values": {tag: text}}]. Get handles and tags from bricscad_read_attributes. Tags match whatever their case.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
updatesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, yet the description adds genuinely new behavior: the operation is atomic ('Changes all of them or none') and tag matching is case-insensitive. It omits whether the change can be reverted via bricscad_undo and what happens if a tag is absent from an insert.

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?

Purpose and the atomicity guarantee are front-loaded, and the update structure follows immediately. The pseudo-JSON shorthand ('updates: [{"handle": ...}]') is slightly schema-redundant and the rambling line breaks hurt scanability, but nothing is wasted.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values needn't be described. For a destructive two-param mutation, the description covers atomicity, tag case rules, and where to get handles — enough to call it safely in one pass.

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 coverage is 0%, so the description must carry the load, and it does for the required param: it spells out the update object shape ({handle, values: {tag: text}}) and the source of those identifiers. The 'timeout' parameter is never mentioned, leaving one of two parameters undocumented.

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 ('Set attribute values on block inserts') with a concrete example ('such as a title block'), and its read counterpart is named explicitly, so an agent can separate it from bricscad_read_attributes at a glance.

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 a clear prerequisite: handles and tags come from bricscad_read_attributes, which implicitly routes reads there. It does not state when-not to use this tool (e.g. non-attribute block properties), so it stops short of full routing guidance.

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