Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_create_entities

Draw CAD entities in a single undo step and return their handles, covering lines, polylines, circles, arcs, text, dimensions, hatches, and block inserts.

Instructions

Draw entities and return their handles. Draws all of them or none, as one undo step.

entities: up to 2000 items, each with a type and an optional layer, which must exist. Points are [x, y] or [x, y, z]. Angles are degrees. layout: a sheet name. The default is the model, whichever tab is current. MTEXT takes format codes, where \P is a line break. Write a literal backslash or brace as \, { or }.

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

Input Schema

NameRequiredDescriptionDefault
layoutNo
timeoutNo
entitiesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that the batch is atomic ('all of them or none, as one undo step') and that handles are returned. It also reveals a validation behavior: layers must exist or, presumably, the call fails. It does not state whether prior drawing state is otherwise touched or what errors look like.

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 atomicity are front-loaded, then parameter notes follow in a compact list-like flow. The mid-sentence line breaks are awkward but every sentence contributes information; nothing is filler.

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?

For a mutation tool with a large union-typed schema and no annotation detail, the description covers the operation's core semantics, failure mode (atomicity), limits, units, and layout targeting. An output schema exists, so return values need not be explained beyond the handle mention.

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

Parameters3/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 the load, and it does for key items: entity list structure and 2000 cap, point dimensionality, degrees for angles, layout sheet semantics and defaults, and MTEXT escape rules. The 'timeout' parameter is never explained, and per-type fields (dimension kind, hatch pattern/scale, polyline bulges, insert attributes) are left entirely to the schema.

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 ('Draw entities') and adds the return value ('return their handles') plus the atomicity guarantee. It does not explicitly contrast with siblings like bricscad_modify_entities or bricscad_erase_entities, so an agent must infer that this creates new entities rather than altering existing ones.

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?

Usage is implied by 'Draw entities' and reinforced by constraints: layers must already exist, up to 2000 items, all-or-none. There is no explicit when-to-use/when-not guidance or routing to alternatives, and no stated prerequisite such as an open drawing.

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