Skip to main content
Glama
U-C4N
by U-C4N

Sheet: Extract Bill of Materials

bom_extract
Read-only

Read AutoCAD block inserts to generate an ISO 7573 bill of materials without altering the drawing. Outputs item rows with quantities, designations, and standards.

Instructions

Walk the INSERTs and return the ISO 7573 item rows. Never modifies the drawing. bom_table is what draws them.

Each row's source is reported: xdata when the ACADMCP_MECH payload supplied it (what std_part_insert writes), attributes when the block's own ATTRIBs did. A block with neither a payload nor a DESIGNATION attribute is skipped rather than guessed at, and skipped counts them.

The whole drawing is read by default — entity_list's 200-entity page is paged through, not taken as a cap, because an item list that stops at the 200th INSERT prints a wrong QTY rather than a shorter one. Pass limit to cap it deliberately; truncated is then true if and only if the cap cut the list. Refusals: an unknown column or group_by field, named with the list of the ones there are.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerNoOnly read INSERTs on this layer; empty reads all.
limitNoStop after this many item records; 0 (the default) reads the whole drawing. `truncated` says whether the cap cut the list.
columnsNoColumns to return; default item, qty, designation, standard, material.
group_byNoField to group identical parts by: designation, standard, material, or '' for one row per insert.designation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses that it never modifies the drawing, how each row's provenance is reported (xdata vs attributes), that payload-less/attrib-less blocks are skipped rather than guessed, that skipped counts them, and the exact `truncated` invariant. This is unusually rich behavioral context for a read tool.

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?

Front-loaded with purpose, then provenance, then paging semantics. Dense but every sentence carries information; the parentheticals ('what `std_part_insert` writes', 'not taken as a cap') are somewhat verbose but justified.

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?

An output schema exists, and the description still supplies the non-obvious return semantics (row source, skipped count, truncated invariant) plus refusal behavior. Nothing an agent needs to call it correctly is 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 coverage is 100% and the schema already documents all four params, but the description adds real meaning: the rationale for limit=0 (a capped list prints a wrong QTY, not a shorter one) and the iff-relationship between `limit` and `truncated`. It adds less on layer/columns/group_by, which the schema covers.

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+resource ('walk the INSERTs and return the ISO 7573 item rows') and immediately distinguishes itself from the sibling that renders them ('`bom_table` is what draws them'). An agent can separate extract vs. draw 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 Guidelines5/5

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

Explicitly says the whole drawing is read by default and why the entity_list 200-page is paged through rather than treated as a cap, then states when to pass `limit`. It also names the refusal cases (unknown column or group_by field), giving clear use/avoid conditions.

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

Deploy Server

Other Tools