How the tools workCopy Anchor Link

Drafts by name. Tools name a draft as <namespace>/<slug>@<rev>, for example ana/nas-box@1: your handle, the device's id, and the revision number. list_my_drafts lists yours, and create_draft answers with the new one's name.

Working copies. Each command (setBody, addPort, and so on) changes a working copy of the draft that the server keeps for your agent between calls. They are the same commands the modeler runs in your browser.

Saving. save writes the working copy to the draft. While you have the draft open in a browser, you rarely need it: your agent's changes show there at once, and the browser saves them to the draft as it saves your own edits. With no browser open, the changes wait in the working copy until save. If the draft changed in the browser since the agent last looked, save refuses unless it is told to overwrite; discard_changes drops the agent's copy instead. See Live sync.

All or nothing. apply_commands runs several commands in one call, in order. If any one is refused, nothing changes.

Access says what a tool may do:

• reads only: it changes nothing;
• makes changes: it changes your working copy, the draft, or what is kept with it (a datasheet);
• makes changes that can drop or replace earlier work: it can't be undone from the agent (dropping a working copy, publishing);
• reaches beyond Rack Maker: it fetches a URL on the internet.

Your agent's client sees the same, as each tool's hints.

Every tool acts as you, with your permissions and limits. See Using AI agents.

The server offers 65 tools. This list is made from their definitions each time the site is built, so it always matches what your agent sees.

DraftsCopy Anchor Link

Find, start, save and drop the drafts the agent works on.

list_my_draftsCopy Anchor Link

List my device drafts. Your devices and parts in the modeler that are drafts or waiting for review, with their draft ids and links.

Access: reads only.

Input: none.

Answers: { drafts: [{ draft, name, status, updatedAt, workingCopy, url }] }: each draft or submission, whether a working copy is kept for it, and its link in the modeler.

get_draftCopy Anchor Link

Get a draft. A draft's spec (your working copy, if you have one), each face's size and flat area in mm, the images traced on its faces (sizes and corners only), and the checklist of what is still missing before publishing.

Access: reads only.

Answers: { draft, status, unsaved, changedElsewhere, url, kind, shape, envelope, mounting, spec, faces, traces, checklist }: faces gives each face's size and flat area in mm, traces the images traced on it (sizes and corners only), checklist what is done and what is still missing, openIssues the user's corrections, and detections how many detections from the user's photos are pending, accepted and rejected, with a nudge.

create_draftCopy Anchor Link

Create a draft. Start a device: { name, maker? } for a new one (a plain 150 × 150 × 40 mm box until you set its body); a part: { name, kind: "part", category } (a 200 × 150 × 3 mm plate until you set its shape: a shelf, tray, bracket, panel…); or { from: "<namespace>/<slug>@<rev>" } for a new revision of a published one (yours) or a copy of someone else's, crediting them.

Access: makes changes.

Answers: { draft, url, next }: the new draft's id, its link, and what to do next.

saveCopy Anchor Link

Save the draft. Write your working copy to the draft, so it shows in the modeler in the browser and in the catalog as a draft. Refuses if the draft changed in the browser meanwhile, unless overwrite is true.

Access: makes changes.

Answers: { draft, saved, url }, or saved: false with a note when there was nothing to save.

discard_changesCopy Anchor Link

Discard the working copy. Drop your unsaved working copy (and the traced corners); the draft stays as last saved.

Access: makes changes that can drop or replace earlier work.

Answers: { draft, discarded: true }.

Modeler commandsCopy Anchor Link

Each is one command of the modeler, the same the browser runs, applied to the draft's working copy. Every one takes the draft it works on, and answers the same way.

apply_commandsCopy Anchor Link

Apply several commands. Run several modeler commands on a draft in one go, in order: [{ type: "setBody", w: 150, … }, { type: "addPort", port: { … } }]. All or nothing: if one is refused, nothing changes. Each command takes the same fields as its own tool. Detections too: { type: "acceptDetection", id: "d3" } (with label, at, size, rotate, itemId, note to correct it), { type: "rejectDetection", id, note }, { type: "updateDetection", id, label }.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setIdentityCopy Anchor Link

Name the device, its maker, and the link to its product or spec-sheet page.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setKindCopy Anchor Link

Say what you are modelling: a device (has ports, stands on a surface or in a rack) or a part that holds or mounts things (a shelf, tray, bracket, panel, plate, spacer), with its catalog category. A part is published as that category; its mounting (setMount) and decks (addDeck) are what make it useful in a rack.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setShapeCopy Anchor Link

Choose the body's shape (default: box). Pick the simplest that matches the silhouette: - box: a rectangular case with rounded upright corners (radius) and bevelled or rounded top and bottom edges (most switches, routers, NUCs). - rounded: a rounded rectangle seen from above whose corners are big (up to half the width: a stadium) or whose bottom edge differs from the top (bottomEdge): a Mac mini, many mini PCs. Measure the corner radius from a photo from above (the corner's arc against a ruler), or estimate from the straight part of each side. - cylinder: round seen from above (diameter): hubs, smart speakers, round workstations; a puck is a short cylinder with big round edges (edgeSize). Its round side is four faces, one quarter each (front, right, rear, left); u runs around the side from the face's left edge (measure along the surface with a tape, or from the angle: u = angle in radians × radius). Things there are drawn on the surface, not cut; photos can't be traced on the round side. - tapered: a box whose top is smaller on some sides (top: { front, rear, left, right } insets, measured horizontally): a front bezel sloping back, a NAS with a slanted front. The slanted faces are flat: their v runs up the slope. - stack: the box plus blocks (a raised section on top, rack ears, a handle). Ports go on the box's faces only; the model's size grows to take in the blocks. - extrusion: a 2D outline (with holes) on the front, right or top face, run straight through: brackets (profile angle or zee), channels, plates (plane top), panels (plane front), shelves (an angle seen from the side). Give a profile ({ kind, w, h, t }) or the outline's corners; the body's size becomes the outline's box and the length. Ports and zones go on the two outline faces only.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setMountCopy Anchor Link

How it mounts: on rack rails (standard 10in, 19in or deskpi-tl1, its height in U, and the flange: the depth from its front to where the ears sit against the rails, usually the faceplate thickness, 2–3 mm), or null to stand on a flat surface. Anything that mounts in a rack (a shelf, a blanking panel, a 1U device with ears) needs this.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

addDeckCopy Anchor Link

Offer a deck: a flat surface devices stand on (a shelf socket). at is its front-left corner in model coordinates (x from the left of the whole model, y from its front, z the height of the surface), size its usable [width, depth]; capacity and maxLoadG are optional limits. A shelf or tray needs one to hold anything.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

updateDeckCopy Anchor Link

Change a deck's fields; null clears one.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

removeDeckCopy Anchor Link

Remove a deck.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setBodyCopy Anchor Link

Set the body: w (left to right), d (front to rear), h (height without feet), radius of the vertical edges, and the bevel or round along the top and bottom edges. All mm. Measure the outside of the case at its widest. On a cylinder w and d are the diameter; on an extrusion the outline stretches with the size.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setFeetCopy Anchor Link

Set the feet as pegs (setBase { kind: "pegs" } by its older name; a base made of solids goes): height (0: none), diameter, inset from the edges for the default four, or their centres [x, y] in model coordinates on the bottom, and round or square.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setBaseCopy Anchor Link

Set the base: what the device stands on. Pick the kind from a photo from the side at table level and one from below: - pegs: separate feet near the corners. Measure their height, diameter (or side) and inset, or give each centre (at). layout "corners-and-middle" for six. - plinth: one base set in from the body's edges (the body seems to float over a smaller, often darker block). Measure its footprint (size, or inset from the body's edges), height and outline (rect with radius, ellipse, stadium, path), and how it meets the body: step, chamfer, cove (a concave curve flaring out into the body: measure its radius, see the server's instructions on curves) or round (convex). tuck: the body's bottom edge curving in to meet it. pad: a rubber pad or ring on its bottom. - rails: parallel runners (NAS units, some switches): count, width, height, inset from the sides, endInset from the ends, along d (front to rear) or w. - none: a flat bottom. custom: keep the height and build the base from solids (addSolid, z < 0). A plinth and rails are made as solids (role "base"), which list_solids shows and updateSolid edits; setBase again replaces them. h is always the height from the table to the body's bottom.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

addSolidCopy Anchor Link

Add a solid: geometry the shapes and presets don't have (a boss, a knob, a raised panel, a handle, a dome, a hood), or a cut (op "cut": a groove, a recess, a vent, taken out of the flat face it runs into). Kinds: extrude (a profile run straight; draft; rims at either end: round, cove, chamfer, flare), box, cylinder, revolve (an [r, a] profile turned round the axis), loft (from one profile to another). Profiles: rect, circle, ellipse, stadium, or a path whose [u, v, bulge] points make arcs. Place it in body coordinates (at, axis), or onFace { face, at: [u, v], depth? } like a port: the profile as seen on that face, running out of it (a cut: depth into it). A cut must be a straight extrude, box or cylinder square to one flat face, and not go through. Ports can't go where a solid covers a face or over a cut. Check it with render_faces { section: "side" } and the faces.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

updateSolidCopy Anchor Link

Change a solid's fields (any but id; null clears one): move it (at), resize it, change its profile, rims, draft, finish or op.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

removeSolidCopy Anchor Link

Remove a solid.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

addPortCopy Anchor Link

Add a port opening (or a row of identical ones). Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item). The reply gives its id.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

movePortCopy Anchor Link

Move a port. Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

updatePortCopy Anchor Link

Change any of a port's fields (kind, label, face, at, rotate, count, pitch, along, size); null clears one.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

removePortCopy Anchor Link

Remove a port.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

addZoneCopy Anchor Link

Add a zone: an area of a face with its own finish (a vent grille, a metal-foam front), flush or sunk in. Ports inside it are cut into it. Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

moveZoneCopy Anchor Link

Move a zone. Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

updateZoneCopy Anchor Link

Change a zone's fields; null clears one.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

removeZoneCopy Anchor Link

Remove a zone.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

addFeatureCopy Anchor Link

Add an LED or a small button. Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

moveFeatureCopy Anchor Link

Move an LED or button. Positions are [u, v] mm on the face (see the server instructions: seen from outside, from the bottom-left corner, centre of the item).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

updateFeatureCopy Anchor Link

Change an LED's or button's fields; null clears one.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

removeFeatureCopy Anchor Link

Remove an LED or button.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setFinishCopy Anchor Link

Set the finish of the body or a zone ("zone:<id>"): a colour, and a preset (matte-plastic, brushed-metal, perforated-grille, metal-foam). Sample the colour from a photo of the real device.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setSourceCopy Anchor Link

Say where a value comes from: measured (calipers, a ruler), datasheet, or estimated. Keys: body.w, body.d, body.h, body.radius, body.edge, body.shape, feet, mount, mass, port:<id>, zone:<id>, feature:<id>.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setMassCopy Anchor Link

Set the weight in grams (null clears it).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setNoteCopy Anchor Link

A note for whoever reopens these measurements: how they were taken, what is still a guess.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setPhotoCopy Anchor Link

Tell the modeler you traced a face on an image of this size (pixels). The image stays with you; only its size is kept, so that corners and points on it can be turned into mm. source "drawing" for a datasheet page.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setCornersCopy Anchor Link

A photo's four face corners, in pixels (y down): bottom-left, bottom-right, top-right, top-left, as seen from outside. Then image_to_face turns points on the photo into mm on the face.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setScaleCopy Anchor Link

A drawing: the two ends of a labelled dimension (pixels) and its length in mm.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setOriginCopy Anchor Link

A drawing: where the face's bottom-left corner is on it (pixels).

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

setSpecCopy Anchor Link

Replace the whole spec (as get_draft returns it). Prefer the other commands; this one is for bulk edits.

Access: makes changes.

Answers: { ok, draft, id?, ids?, unsaved: true, problemsWithThis?, problems }: the id of what an add command created, and how many problems the spec has now (with the ones about what this command touched). A refusal says why, and nothing changes.

Checking the workCopy Anchor Link

See what the agent built, and turn pixels on a photo into millimetres.

image_to_faceCopy Anchor Link

Image pixels to face mm. Turn points on the image traced on a face (pixels, y down) into positions on the face ([u, v] mm), correcting the photo's perspective. Needs setPhoto and setCorners (a photo) or setScale and setOrigin (a drawing) for that face first.

Access: reads only.

Answers: { face, points: [{ px, at, note? }] }: each pixel's [u, v] mm on the face, noted if it falls off the face.

build_summaryCopy Anchor Link

Summarise the model. What the modeler's builder makes of the spec, counted from it without building: the triangle count, the port anchors, the materials, about how big the GLB will be, every error and warning, and the checklist of what is still missing. Use render_faces to see it.

Access: reads only.

Answers: { draft, unsaved, changedElsewhere, shape, envelope, mounting, triangles, triangleTarget, anchors, materials, glbBytesEstimate, glbTarget, errors, warnings, checklist }.

render_facesCopy Anchor Link

Render the faces. See what you built: each face drawn straight on as seen from outside (the same view as a straight-on photo of it), with its outline, the flat area (dashed), a 10 mm grid and ruler, zones in their colours, every opening with its port's name (rows once, with their count), LEDs and buttons, what can't be cut in red, the base and solids seen from that side (the base's height beside it), where solids cover the face (nothing can be cut there) and the cuts; overview: true adds an isometric wireframe of the whole device; section: "side" (or "front") adds a cut through the middle (sectionAt: elsewhere, mm) to check a profile, a plinth's curve or a groove's depth against a side photo. Returns PNG images (format: svg for SVG) and the same as a text listing. Compare each picture with the user's photos or drawings of that face: the position, size, spacing and name of every opening, the zones, the LEDs. Where they differ, correct the spec (movePort, updatePort, moveZone, …) and render again until they match.

Access: reads only.

Answers: A text listing of each face (its size, flat area and everything on it), then one image per face drawn (PNG, or SVG with format: "svg"), and the overview when asked for. Faces that did not fit this call's pixel budget are listed as not drawn.

DatasheetsCopy Anchor Link

Keep a device's datasheet PDF with it, privately.

attach_datasheetCopy Anchor Link

Attach a datasheet. Keep a copy of the device's datasheet (a PDF at a public http(s) URL, up to 15 MB) with the draft, as the modeler's Datasheets panel does: the server fetches it and stores it privately (only the user and admins can open it; the public page shows only its link). The device links to the URL if it had no datasheet link yet. Read the PDF yourself for the numbers. For a PDF on the user's computer, use create_datasheet_upload instead.

Access: makes changes; reaches beyond Rack Maker (fetches a URL).

Answers: { draft, datasheet: { id, name, bytes, source }, note?, private, deviceLink, url }: the kept copy, who can open it, and whether the device now links to the URL.

create_datasheet_uploadCopy Anchor Link

Upload a datasheet from this computer. Get a link to upload the device's datasheet, a PDF on the user's computer (up to 15 MB), and keep a private copy with the draft, as the modeler's Datasheets panel does (only the user and admins can open it). Then upload the file yourself with a shell command: curl -sS -T '/path/to/datasheet.pdf' '<url>' (a PUT; curl --data-binary @file.pdf <url> also works). The link works once, for 10 minutes, for this draft only, and needs no sign-in header. This is the only way a file reaches Rack Maker from you, and only a datasheet PDF: never upload photos (read them yourself and send numbers). Read the PDF yourself for the numbers. For a PDF at a public URL, use attach_datasheet.

Access: makes changes.

Answers: { draft, upload: { url, method, expiresAt, once, maxBytes }, curl, how, private, url }: the one-time link, the command to upload the PDF with, and what the link answers.

DetectionsCopy Anchor Link

What the detector found on the user's photos, in their browser: candidates to accept, reject or relabel. Numbers and labels only; the photos never reach the server.

list_detectionsCopy Anchor Link

List detections. What the detector found on the user's photos of the device, run in their browser: candidate ports (by kind), vents, LEDs and buttons, each with a label, a confidence (0–1), its box on the face ([u, v] centre and [w, h] mm), the next best labels, and the user's notes. Default: the pending ones. Read them with the user's words and annotations; confirm uncertain ones with the user; then accept, reject or relabel each.

Access: reads only.

Answers: { draft, detections: [{ id, face, label, what, confidence, at, size, rotate?, holes?, alternatives?, status, became?, foundAs?, note?, by? }], counts, how }: each detection with its box in face mm, and how many are pending, accepted and rejected.

accept_detectionCopy Anchor Link

Accept a detection. Make what a detection shows, with the ordinary commands, in your working copy: a port of its kind (turned on end, and with its own opening size when it differs from the standard one by more than 0.8 mm), a zone with a grille finish for a vent, or an LED or button. Correct it on the way: label, at, size, rotate. Say why in note when it helps the user. An "opening" of no known kind needs a label.

Access: makes changes.

Answers: { ok, draft, id, unsaved, problems, accepted, became }, as a command answers: the id of the port, zone or LED it became.

reject_detectionCopy Anchor Link

Reject a detection. Drop a detection that is nothing (a screw, a label, a shadow) or that you won't model, with a note saying why. The user sees it rejected, live.

Access: makes changes.

Answers: { draft, rejected, pending }: how many are still pending.

update_detectionCopy Anchor Link

Relabel or adjust a detection. Relabel a detection (the kind you or the user think it is), move or resize its box, or note something on it, without accepting it yet: e.g. when you want the user to confirm first. The label as found is kept (foundAs).

Access: makes changes.

Answers: { draft, updated }: the detection as it is now.

PublishingCopy Anchor Link

Submit to the catalog.

publishCopy Anchor Link

Publish. Save, then submit the device or part to the catalog under CC BY-SA 4.0. With contributor access it is published in your namespace with its model file (GLB), built here from its spec and credited to the user (if that build fails, it is published with its spec and the user's browser attaches the model file later; the answer says which). Without contributor access, the measurements go to an admin for review and it is drawn from its spec meanwhile. Ask the user before publishing.

Access: makes changes that can drop or replace earlier work.

Answers: { draft, status, note?, model, asset?, url }: published or review, and what became of the model file (built here, with its asset id, or attached by a browser later).

More toolsCopy Anchor Link

Newer tools, not grouped yet.

list_annotationsCopy Anchor Link

List annotations. The user's annotations on the draft's device: pins and boxes on its faces or model, and notes on its ports, zones and measurements. Kinds: issue and wrong ("this is wrong": corrections for you to make), measure (a number someone should measure), note. Each has its number (#3), where it is (face and [u, v] mm), its text, replies, and how it was resolved. Default: the open ones. Read them before changing a device, fix every issue, and resolve each with a note on what you changed.

Access: reads only.

Answers: JSON text; see the description.

add_annotationCopy Anchor Link

Add an annotation. Pin a note on the device for the user, shown at once in their modeler: most often kind "measure" to ask them to measure something you can't see well ("measure the distance from the left edge to the first USB port"), with an anchor where it is. Also "note" (something they should know) or "issue" (a problem you found but can't fix). Their answer comes back as a reply (list_annotations).

Access: makes changes.

Answers: JSON text; see the description.

resolve_annotationCopy Anchor Link

Resolve an annotation. Mark an annotation resolved, with a note saying what you changed ("moved usb-c-1 3 mm left, to [42, 12]") or why nothing needed to change. Do this after fixing each issue the user raised; the user sees it resolved, live.

Access: makes changes.

Answers: JSON text; see the description.

reply_to_annotationCopy Anchor Link

Reply to an annotation. Answer an annotation without resolving it: ask the user what they meant, or for a measurement you need, when a correction doesn't make sense to you. The user sees the reply under it, live.

Access: makes changes.

Answers: JSON text; see the description.

list_solidsCopy Anchor Link

List the solids. The draft's base in words and its solids (added and cut), each in words and as data (what updateSolid changes), where it reaches in the model, which faces it covers (nothing can be cut there) or which face it is cut into, and its problems.

Access: reads only.

Answers: JSON text; see the description.

report_modeling_gapCopy Anchor Link

Report a modelling gap. Tell Rack Maker's admins about a shape of the device that the modeler can't represent, instead of hitting a dead end. Use it only after trying to compose the shape from the modeler's solids (extrude, revolve, loft, box, cylinder, with rim fillets/chamfers, added or cut) and presets. Describe the shape in words and mm, what you tried, and optionally the primitive that would do it. Text only: never include photos, links to them, or personal data. It is filed for the admins with the draft; tell the user it was filed.

Access: makes changes.

Answers: JSON text; see the description.

define_formCopy Anchor Link

Define the measurement form. Build a measurement form for this device from what you know of it (its datasheet, photos, similar devices): the few numbers the user can measure with calipers or a ruler, grouped in sections in the order to measure them, each with how to measure it, a sensible range, your best value and its source (estimated until the user confirms). Then formulas turn them into the spec: body.w = case_w, the u of a row of ports = margin + i*pitch, a zone = case_w - 2*bezel. Values worked out from others are measurements with expr. Everything is optional but the sections. Clients that render MCP Apps show the form inline in the chat: the user sees every value with its unit, source and the formulas it feeds, a drawing of the face, and can edit values or flag one as wrong right there; everyone else gets the same as text. It is live in the user's open modeler too (the Measurements panel), where editing a value re-renders the 3D model at once. After defining it, show it to the user and ask them to check each value; apply what they correct with set_measurements, and fix formulas they say are wrong with set_formula.

Access: makes changes.

Answers: JSON text; see the description.

get_formCopy Anchor Link

Get the measurement form. The draft's measurement form: every measurement with its value, unit, source, how to measure it, the formulas it feeds and their results, errors, the user's open flags, and checks (a part bigger than its face, an opening over an edge, a value that looks 25.4× off). Clients that render MCP Apps show the form inline in the chat: the user sees every value with its unit, source and the formulas it feeds, a drawing of the face, and can edit values or flag one as wrong right there; everyone else gets the same as text. It is live in the user's open modeler too (the Measurements panel), where editing a value re-renders the 3D model at once.

Access: reads only.

Answers: JSON text; see the description.

show_formCopy Anchor Link

Show the measurement form. Show the user the draft's measurement form to check and correct: inline in the chat where the client renders MCP Apps, as text otherwise (with the link to the modeler). Clients that render MCP Apps show the form inline in the chat: the user sees every value with its unit, source and the formulas it feeds, a drawing of the face, and can edit values or flag one as wrong right there; everyone else gets the same as text. It is live in the user's open modeler too (the Measurements panel), where editing a value re-renders the 3D model at once. Afterwards, read what they changed or flagged (get_form, list_flags).

Access: reads only.

Answers: JSON text; see the description.

set_measurementsCopy Anchor Link

Set measurements. Set several measurements at once, as the user gives them ("the case is 151.2, the bumper 1.5"): each { id, value, source }. Mark what the user measured as measured, what came from the datasheet as datasheet. Every formula is worked out again and the spec follows; the answer lists what changed, errors (a negative size, a value out of range) and checks. The inline form calls this too when the user edits a value.

Access: makes changes.

Answers: JSON text; see the description.

set_formulaCopy Anchor Link

Set a formula. Drive a spec field by a formula over the measurements (expr), or drop its formula (expr: null; the field keeps its number). Several fields with one formula (paths) each get their index as i: the u of lan-1…lan-4 = margin + i*pitch. Units are checked: a formula that gives mm² or a count where mm are due is refused, as are unknown names and cycles. Use it to fix a formula the user says is wrong.

Access: makes changes.

Answers: JSON text; see the description.

explainCopy Anchor Link

Explain the formulas. Every measurement and formula with its worked-out value, as text: what each spec field is computed from, which fields each measurement feeds, errors, open flags and checks. Use it to tell the user how their measurements are used, or to check your formulas.

Access: reads only.

Answers: JSON text; see the description.

list_flagsCopy Anchor Link

List the user's flags. The values and formulas the user marked as wrong (in the modeler's Measurements panel or the inline form), each with their note: open ones first. Fix each (set_measurements, set_formula, or ask the user), then resolve_flag it with what you did.

Access: reads only.

Answers: JSON text; see the description.

resolve_flagCopy Anchor Link

Resolve a flag. Close a flag the user raised, once you have fixed what it points at (or explained why it is right): resolution says what you did, and the user sees it next to the value.

Access: makes changes.

Answers: JSON text; see the description.

flag_valueCopy Anchor Link

Flag a value as wrong. The user marks a measurement ("measurement:<id>") or a formula ("formula:<path>") as wrong, with a note. The inline form calls this; list_flags reads them.

Access: makes changes.

Answers: JSON text; see the description.