Kamai

Get a blueprint's processing state and readiness.

get_blueprint

Cancel a processing job that is still pending or running. A job that already finished or failed cannot be cancelled and is reported as such. Cancelling marks the job; work already in progress on the Kamai side may still run to completion.

cancel_job

Create a folder on a blueprint, under an existing folder or under the sheet's root. parent_id must be a folder from list_folders; omit it to create under the root. A missing or non-folder parent is refused, not guessed. Refer to the blueprint by name.

create_folder

Create a new Kamai project to hold blueprints.

create_project

Step 2 of 2: finalize a blueprint upload started with `request_blueprint_upload`. Call this after PUTting the file to the signed URL. Validates the uploaded file, files it under the project, and starts the processing pipeline. Returns the job_id, the project_id and the project_name. When telling the user where the blueprint landed, use `project_name`, not the id.

finalize_blueprint_upload

Ingest a blueprint PDF the user attached in this ChatGPT message and start processing. Attach the blueprint PDF to your message, then call this tool. Returns the job_id and project_id; uses the user's Default Project when project_id is omitted. ChatGPT web only.

ingest_blueprint_from_chat

List a blueprint's individual take-off elements: one row per room, wall, door, window or object, with its class, the folder it sits in on the drawing, its measured area or length, and its outline. This is the per-element counterpart to `view_takeoff`, which returns only per-class totals — use view_takeoff for quantities, and this when the user asks about particular elements, their sizes, where they are, or what is inside one folder. Narrow it with `cls`, `folder` and `name` (case-insensitive substring match). Kamai's geometry endpoint has no filter of its own, so this tool reads the blueprint and filters here: `matched`, `filter_scanned` and `filter_complete` say what the filter actually saw, and `filter_complete` false means elements exist that were never checked. `rings`, `lines` and `pts` are flat [x0,y0,x1,y1,...] integer paths in the blueprint's own drawing space, where the page is `grid` units wide. They give shape and position, not size: quote `area` and `len` in `units` for measurements, and never compute a measurement from the coordinates. Both are null when `needs_scale` is true, and provisional when `scale_unconfirmed` is true. Each row's `id` is the stable local id for `update_elements` and `move_elements`. Folders are not in this list (they have no shape) — use `list_folders` for those. Outlines are bulky, so pages are small: `limit` defaults to 50 and is held to 100 while `include_geometry` is true. A page is also held to a size budget, so `returned` can be smaller than `limit` — a single traced wall can carry thousands of points. Pass include_geometry false for a cheaper index of up to 400 elements with names, classes and measurements only. Always check `truncated` and read `notes` before telling the user what a blueprint contains — a truncated page is not the blueprint. Refer to the blueprint and project by name in your replies. Never show a raw id unless the user asks for one.

list_elements

List a blueprint's legend folders: id, name, parent, and colour. Geometry tools skip folders because they have no shape, so call this when the user asks to create, rename, recolour, or move items between folders. Pass a folder's `id` to create_folder (as parent_id), update_elements, or move_elements. Do not show raw ids unless the user asks for one. Refer to the blueprint and project by name.

list_folders

List the authenticated user's Kamai projects (most-recently-modified first).

list_projects

Get one processing job's status, progress and error, if any.

get_job