swdraw
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SWDRAW_PROFILES | No | Path to the profiles folder containing house_style.yaml, title_block.yaml, numbering.yaml. If not set, bundled profiles are used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| swdraw_validate_specA | Check a drawing spec (YAML/JSON, absolute path) for missing keys, bad points and dimensions without |
| swdraw_build_drawingA | Build the ACTIVE SolidWorks drawing from a spec: scale, clear, layout, sections, details, self-checked
dimensions, GD&T, leader notes, notes block, title block, fonts, PDF/PNG export. Does not save.
|
| swdraw_reviseB | Apply a revision to a drawing (active, or args.drawing): rev row, REV box, approval, SEE NOTE n, view shifts, moving dims/GTols to model points. Keys: rev, row, desc, date, drawn, approved, approver_name, approved_date, finish_note, shift_views, notes_pos, move_dims, move_gtols, save. |
| swdraw_renumberB | Reference-safe renumber of a part and its drawing (part Save As with the drawing open, notes swap, drawing Save As, dependency check, optional supersede/folder rename/verify). Keys: drawing, old, new, old_parent, new_parent, description, revision, part, notes_lines, save, supersede, rename_folder. |
| swdraw_notesB | action 'replace': delete and re-insert the numbered NOTES: block (args: lines, pos [mm], values, drawing, save). action 'dedupe': keep the numbered block, delete copies that lost their numbering (args: pos, drawing, save). |
| swdraw_export_pdfA | Export the active drawing (or args.drawing) to PDF, plus a PNG preview for visual checking (args.path, args.png). |
| swdraw_tidyB | Move files that aren't live out of a working folder. DRY RUN unless dry_run is false. Keys: working, keep (glob list), superseded, move_folders, dry_run. |
| swdraw_registerB | Generate the drawing register workbook (Register / Revision History / Numbering). Keys: out, title, drawings [{number,title,type,parent,file}], revisions [{number,rev,date,description,by,approved,status}], or data: path to a YAML/JSON file with those keys; numbering_profile. |
| swdraw_numberC | Part numbers. action 'check' (args.numbers), 'next-part' (args.assembly, args.used), 'next-assembly' (args.used, args.discipline). |
| swdraw_diagnosticsB | Read-only probes of the active drawing: 'views', 'selection', 'annotations'; or 'refs' with args.paths. |
| swdraw_run_scriptB | Run one of your own Python scripts from SWDRAW_SCRIPTS_DIR with swdraw importable
( |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a fairly distinct operation (validate, build, revise, renumber, export, tidy, register, number, diagnostics, notes, script). There is minor overlap: swdraw_build_drawing already handles PDF/PNG export while swdraw_export_pdf also does it, and swdraw_revise touches notes/REV that swdraw_notes also manages, which could cause slight misselection.
All tools share the swdraw_ prefix and snake_case, giving a predictable namespace. Most follow verb_noun (validate_spec, build_drawing, export_pdf, run_script) but a few are bare verbs (revise, renumber, tidy) or nouns (notes, diagnostics), a minor deviation from a strict pattern.
11 tools is well within the ideal 3-15 range and each maps to a meaningful stage of the drawing lifecycle. No tool appears redundant filler.
The surface covers validate, build, revise, renumber, notes, export, tidy, register, number, diagnostics, plus an escape hatch via run_script, which is strong lifecycle coverage. Minor gaps: build explicitly does not save, and there is no dedicated read/get or delete operation, but agents can work around these.