Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_drawing_info

Read-only

Retrieve BricsCAD drawing metadata—name, path, read-only/modified state, units, limits, entity count, and layouts—to audit or verify the current drawing before editing.

Instructions

Describe the current drawing: name, path, read-only and modified state, units, limits, entity count and layouts.

extents and limits describe current_layout only, which may be a sheet rather than the model.

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_drawing_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: extents and limits reflect current_layout only, which may be a sheet rather than the model — a caveat an agent could not infer from the schema or annotations. It stops short of noting failure behavior when no drawing is open, but the key interpretive risk is disclosed.

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 core purpose before the caveat. The field enumeration is compact and every clause carries information; nothing is repeated from the schema or annotations.

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, the description needn't document return values, and with zero parameters there is no schema gap to fill. It covers purpose and the one ambiguous semantic (layout scoping). It could be more complete by stating behavior when no drawing is loaded, but that is the only material omission.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly adds no parameter discussion and instead spends its words on what the returned fields mean, which is the appropriate use of space here.

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 ('Describe') and a specific resource ('the current drawing'), then enumerates exactly what is returned: name, path, read-only/modified state, units, limits, entity count, layouts. That field list lets an agent distinguish this read-only inspection tool from siblings such as bricscad_status or bricscad_list_layouts without opening a schema.

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 only implied: the name plus 'the current drawing' signals this is the tool for inspecting the active document's metadata. There is no explicit when-to-use versus alternatives (e.g., versus bricscad_status or bricscad_list_layers) and no mention of preconditions such as requiring an open drawing.

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