Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_audit_report

Read-only

Audits a BricsCAD drawing to report empty layers, unused blocks, missing xrefs, entities above zero elevation, and off-standard layer names.

Instructions

Report empty layers, unused blocks, missing xrefs, entities not at zero elevation, and off-standard layer names.

Each section has a total count and up to sample_limit items. Blocks and layers used only inside other blocks count as used, and a dynamic block counts as used through its anonymous states. Layers 0 and Defpoints are never reported.

allowed_layers: name patterns such as ["A-", "S-"], ignoring case. Leave it out to skip this check.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
sample_limitNo
allowed_layersNo

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, but the description adds real domain behavior: block/layer usage counted transitively through nested blocks and anonymous dynamic-block states, and Layers 0 and Defpoints permanently excluded. It also states each section carries a total count, which tells the agent the report is aggregated rather than raw. It does not mention whether a drawing must be open or how long the audit takes, which is where a timeout default of 120 becomes relevant.

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?

The check list is front-loaded in the first sentence, followed by only the behavioral rules an agent could not infer. Every sentence carries distinct information, with no restatement of the title or the name.

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?

An output schema exists, so return structure need not be explained, and the description still usefully flags per-section counts and truncation. Parameter coverage and audit semantics are adequate for this complexity; only timeout behavior and any drawing-open precondition are missing.

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 the parameter meaning, and it does for two of three: allowed_layers is explained as case-insensitive name patterns with example syntax and an explicit skip behavior, and sample_limit is tied to the 'up to sample_limit items' truncation rule. The timeout parameter is left entirely unexplained, which is the remaining gap.

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?

The opening sentence names the exact checks performed: empty layers, unused blocks, missing xrefs, non-zero elevation entities, and off-standard layer names. That is a specific verb-plus-resource statement that clearly separates it from siblings like bricscad_list_layers or bricscad_list_blocks, which enumerate rather than audit.

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?

The only when-to guidance is parameter-specific: 'Leave it out to skip this check' for allowed_layers. Nothing states when to pick this audit over the list_* siblings, whether it requires an open drawing, or what preconditions exist, so the agent must infer the context of use.

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