build123d-mcp

Overview Schema Source Related Servers Discussions Admin

inspect_drawing

Read-only

Inspect 2D CAD drawings to extract bounding boxes, face/edge counts, annotation metadata, and structural lint. Also parses SVG files for page size, layers, text positions, and element counts.

Instructions

DEPRECATED (#465) — moved to draftwright; off by default in 0.4.0, removed in 0.5.0. Calling it explains the replacement. Structured bbox and annotation report for a 2D drawing.

Two modes:

1. Session mode (default): inspects objects registered via annotate()/show().
   Returns per-object bounding boxes, face/edge counts, annotation metadata
   (label string, measured length, Leader tip/elbow), and structural lint.

2. SVG mode (svg_path set): parses an SVG file from disk and reports page
   size, layer ids, text content + positions, and element counts. Decouples
   inspection from the build-and-register ceremony — works on SVGs from any
   source (CI artifacts, third-party exports, prior runs).

Use annotate(result, name) instead of show(result.shape, name) when building
with build123d_drafting so metadata is captured:

    from build123d_drafting import Dimension, Draft
    draft = Draft(font_size=2.5, decimal_precision=1)
    w = Dimension((-20, -10, 0), (20, -10, 0), "below", 8, draft, label="40")
    annotate(w, "width_dim")

For vanilla build123d.ExtensionLine/DimensionLine, pass the label explicitly:

    w = ExtensionLine(border=[...], offset=6, draft=draft, label="40")
    annotate(w, "width_dim", label="40")

Args:
    objects: comma-separated object names (default: all). Session mode only.
    svg_path: path to an SVG file on disk. Switches to SVG mode.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`objects`	No
`svg_path`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.27May 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses what each mode inspects and reports: per-object bounding boxes, face/edge counts, annotation metadata, structural lint, page size, layer ids, text positions, and element counts. It also discloses deprecation behavior ('calling it explains the replacement') and mode-switching behavior.

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?

The description is front-loaded with the deprecation warning and purpose, and it is well-structured with numbered modes and an Args section. It is fairly long and includes two code blocks, so it is not maximally concise, but every section earns its place given the migration guidance and two modes.

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 two-parameter deprecated tool with a readOnly annotation and an output schema, the description covers purpose, mode selection, parameter semantics, return contents, deprecation behavior, and migration path. Nothing critical is missing for an agent to call it correctly or decide to use the replacement.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description fully compensates with an Args section defining objects as comma-separated object names defaulting to all and limited to session mode, and svg_path as the path to an SVG file that switches to SVG mode. The code examples add further semantic clarity about annotation labels.

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 description opens with a deprecation notice and then states a specific verb and resource: 'Structured bbox and annotation report for a 2D drawing.' It further clarifies two distinct modes, session and SVG, which separates it from siblings like inspect_part and lint_drawing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says the tool is deprecated and moved to draftwright, with version behavior, so an agent knows to use the replacement. It also gives clear mode-selection guidance: session mode is default, SVG mode is triggered by svg_path, and migration examples show annotate(result, name) instead of show().

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