Skip to main content
Glama

inspect_drawing

Read-only

Summarizes a CAD drawing's format/version, scale, units, bounds, entity counts, layers, text, sheets, and unreadable parts in one call to assess it before reading or editing.

Instructions

Summarize a drawing: format and version, paper, coordinate units and scale (real mm per unit; for Jw_cad per layer group), bounding box, entity counts by kind, layers, the first texts, sheets or pages, and what could not be read. Uses 1 call.

path: a drawing file inside the working folder (or an .ir.json.gz file). use_edits: send the working copy if edit_drawing made one (default true). pages: for PDF, pages like "1-3,5". sheet: a sheet or layout name if the drawing has several.

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": {
      "path": "<path>"
    },
    "name": "inspect_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
pagesNo
sheetNo
use_editsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description adds real context beyond that: the exact inventory of what is returned, the admission that some content may be unreadable ("what could not be read"), and the cost note "Uses 1 call." The cost disclosure is especially valuable for an agent budgeting calls. It does not describe output structure in detail, but with no output schema the enumerated return list carries most of that burden.

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 summary line is front-loaded with the most important content (what comes back, and the one-call cost), and each parameter gets a single tight clause. It is dense but every line earns its place. Minor cost: the parenthetical about Jw_cad layer groups is a niche detail sitting mid-sentence in the primary summary.

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?

With no output schema, the description takes on the return-value burden and does so by enumerating the summary's fields, including failure reporting. All four parameters, one required, are explained, and the sibling reference to edit_drawing clarifies the use_edits lifecycle. Nothing an agent needs to call this correctly appears to be missing.

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?

Schema description coverage is 0%, so the description must carry all four parameters, and it does: path accepts a drawing in the working folder or an .ir.json.gz file, use_edits is a boolean defaulting to true that selects the edited working copy, pages takes PDF ranges like "1-3,5", and sheet takes a sheet or layout name. The page-range syntax and the .ir.json.gz alternative are meaning the schema does not provide at all.

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?

The description opens with a specific verb and resource ("Summarize a drawing") and then enumerates exactly what the summary contains: format/version, paper, units and scale, bounding box, entity counts, layers, first texts, sheets/pages, and unreadable items. This is far more than a restatement of the name. It stops short of naming how it differs from query_drawing or render_drawing, so an agent must infer the split from the verb alone.

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 conveyed indirectly through parameter notes: use_edits says to send the working copy "if edit_drawing made one," and pages/sheet are scoped to PDFs and multi-sheet drawings respectively. There is no explicit statement of when to prefer this over query_drawing or render_drawing, and no precondition such as "call this first before editing." The guidance is implied rather than declared.

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