Return the identity, site, and roles of the authenticated CLM user.

Call this first: it confirms authentication is actually working (triggering a token refresh if needed) and its site_id is the default most other tools use for their site_id parameter.

List CLM domain enums and their known integer values.

Several API fields (e.g. shipment/lean-card status, severity) are undocumented integer enums in the spec — real member names are not yet known (see PLAN.md). Tools accepting one of these enums take either the int value shown here or its placeholder name (e.g. "UNKNOWN_3") interchangeably.

Search shipments (native CLM and KonsHub-linked) by free text, scoped to a site.

List shipments for the cockpit list view: filtered, searched, ordered, and paged, scoped to the site and the caller's team visibility.

Shipment counts for a site broken down by status bucket (open, approved, completed, cancelled/rejected).

Retrieve the full internal shipment record by id (up to 142 possible fields, most absent for any given shipment). Prefer clm_get_shipment_summary for a smaller, external-facing view.

Retrieve a shipment's smaller, external-facing summary (native CLM or KonsHub-linked).

List all comments posted on a shipment, with commenter display info.

Retrieve the audit/event log history for a shipment or related connected entity, ordered chronologically.

Retrieve the day-wise timeline for a single shipment.

List all non-deleted incidents/findings raised against a shipment.

Retrieve the full detail of a single incident/finding.

List all site equipment, split into bookable and non-bookable groups, for the equipment management grid view.

List equipment timeline entries (bookings) for the cockpit equipment list view: filtered, searched, sorted, and paged.

List lean cards (working packages) for a site, filtered by status.

Count of lean cards (working packages) for a site, broken down by status (overdue, active, pending, completed).

List material handover summaries for a site, filtered by status and date range.

Full details of a single material handover, including its event history and equipment usage.

Weekly shipment count grid for a site's active unloading zones.

Daily weather records (temperature, wind speed, symbol) stored for a site within a date range.

List CLM API operations reachable via clm_invoke.

Filter by exact tag (e.g. "ShipmentCommand") and/or a case-insensitive search substring against the operation name or summary. Use clm_describe_operation on a result to get its full input schema before calling clm_invoke.

Describe one operation: its resolved JSON Schema request body (for a POST operation) or query parameters (for a GET operation), and its response shape — everything needed to build valid clm_invoke params.

Execute any operation listed by clm_list_operations.

params is validated against the operation's resolved schema before the HTTP call. A *Command operation (a write) is refused if the server was started with CLM_ENABLE_WRITES=false.

Creates a new incident/finding against a CLM, KonsHub, or equipment-booking shipment, links it to the shipment, and recalculates the shipment's incident counts. A background command is queued afterwards to generate thumbnails for the incident's attached files, and, if the shipment is already completed, to trigger PDF regeneration.

Soft-deletes an incident by marking it as deleted (IsMarkedToDelete) rather than physically removing it, then recalculates the owning shipment's incident counts to exclude it.

Updates the remark, attached files, and finding type of an existing incident, then recalculates the owning shipment's incident counts and re-queues thumbnail generation for the updated files.

Registers an uploaded lean document (an Excel workbook used to bulk import/refresh lean cards) for a project/site if it does not already exist, then queues it for background processing that parses the workbook and creates or updates the corresponding lean cards.

Creates a new lean card (working package) for a project/site, assigning it to a sender and recipient team, computing its initial status, and setting the access-control roles that determine who can read or update it. Also queues background jobs to refresh site-structure and team grouping counts.

Updates an existing lean card's location (building/floor/laydown area), comment, dates, archived flag, volume, and estimated transport unit; recalculates its status; and queues background jobs to re-sync site-structure and team grouping counts using the old and new values.

Finalizes the working-package import: creates the lean document record for the uploaded file if one does not already exist, then queues a background command that creates or updates the actual lean cards from the previously mapped Excel data.

Saves the user-selected mapping between Excel columns and lean card fields (activity id, date format, sender/recipient team) for a previously uploaded working-package file, then queues background building of a preview of the resulting working packages by matching rows against existing teams and lean cards, notifying the uploading user of the outcome.

Sends an email notification, in each recipient's preferred language, to the members of a lean card's (working package's) sender team informing them that its start/end dates have changed.

Queues the initial background processing of an uploaded working-package Excel file: reading the selected sheet, parsing its rows/columns into a temporary upload record, and notifying the uploading user once processing completes, in preparation for the header-mapping step.

Toggles a handover's status between InProgress and Paused, appending a new handover event capturing the note and photos for the change, and updates the parent shipment's aggregated handover status. Pausing also queues a background job to generate thumbnails for the responsible-person photos of that event.

Marks a handover as Completed: appends a completion event, stores the final material/responsible-person photos and note, computes the total time spent by summing the durations between paired handover events, optionally attaches the responsible person resolved from a QR-code scan, updates the parent shipment's aggregated handover status (triggering PDF regeneration if the shipment itself is now complete), and queues a background job to generate thumbnails for the final photos.

Creates a new material handover for a CLM or Konshub shipment, snapshotting the shipment's bookable equipment and assigning a sequential handover number, then updates the shipment's aggregated handover status/counters and queues a background job to generate thumbnails for the uploaded material photos.

Records the actual usage (unit count or number of time slots, depending on the equipment's price type) for a single planned/bookable equipment item on a handover, recalculates that item's actual total price, and rolls the aggregated actual usage/price back up into the shipment's equipment timeline.

Adds a new comment to a shipment, attributed to the current user.

Transitions a shipment to a new status (approved, waiting/ongoing/unloading, rejected/withdrawn, cancelled at transit, or completed), updates grouping counts, and triggers background processing (e.g. notifications) for the status change.

Deletes an existing shipment comment.

Discards a shipment: if the shipment is still an in-progress wizard draft it is deleted entirely; if it has already been submitted, only its pending edit draft (and smart-wizard draft) is cleared, leaving the submitted shipment intact.

Queues generation of the cockpit daily report PDF (scheduled shipments, equipment, and ad-hoc shipment summaries) for background processing; once generated, the requesting user is notified.

Requests (and returns, if already available) the generated PDF report for a shipment in the given language; if no PDF has been generated yet, this queues background PDF generation and returns immediately without a URL.

Saves the booking date step of the shipment wizard: for a shipment still being created it applies the booking date, express-shipment flag, and lean card directly; for an already-submitted shipment being edited, the change is stored as a pending draft.

Saves the material-selection step of the shipment wizard: for a shipment still being created this sets its materials and recipient team directly; for an already-submitted shipment being edited, the change is stored as a pending draft rather than applied immediately.

Saves the final "other info" step of the shipment wizard (on-site responsible person, sustainability/vehicle info, etc.), finalizing the shipment: persists the additional responsible persons and remaining shipment details, then triggers a background command to complete post-save processing.

Saves the timeslot step of the shipment wizard: resolves the selected zone (and its waiting area, if any), then for a shipment still being created applies the schedule window and equipment reservations directly, or for an already-submitted shipment being edited, stores the change as a pending draft.

Saves the unloading/vehicle step of the shipment wizard: for a shipment still being created it sets the selected vehicle's name, type, ID, and key directly on the shipment; for an already-submitted shipment being edited, the change is stored as a pending draft.

Queues a background job to notify the shipment's recipient that a shipment has been requested, sending the "shipment requested" email in every supported language once the shipment is found.

Updates the text of an existing shipment comment.

Execute ShipmentCommand/UpdateShipmentStatus (a write operation).

Creates or updates an ad-hoc (walk-in, non-wizard) shipment: if a shipment with the given ID already exists it is updated, otherwise a new one is created and a background command is queued to finish processing it (e.g. thumbnail generation, notifications).

Creates, updates, or removes a team's saved sustainability address: marking an address as not-favourite deletes it, otherwise the address (identified by item ID) is updated if it already exists or created new for the given team.

Recalculates and persists a bookable site equipment's daily usage aggregate for the given date, tallying open and approved shipments/bookings that use the equipment that day against its total available time; the aggregate record is removed if total usage becomes zero.

Creates a new site equipment booking submitted from the mobile app in a single call, covering booking date/slots, transport info, and other info (responsible persons, photos), then queues a background command that finalizes the booking (timeline creation and approval notifications).

Creates a new site equipment master record (creating its calendar reservation object and, if bookable, publishing an availability-set command) or updates an existing one (recreating/updating its reservation object and queuing a background command to refresh its zone attachment).

Permanently deletes a site equipment record and queues background commands to remove its zone attachment and, for bookable equipment, its booking prerequisites.

Soft-deletes an equipment booking comment by marking it as deleted (it is excluded from subsequent reads but not physically removed).

Soft-deletes an unplanned equipment usage record (marks it as deleted), removes its associated timeline entry, and logs an event.

Discards an in-progress site equipment booking: permanently deletes it if it is still a drafted (not yet finalized) booking, or clears its in-progress draft data if it is an existing valid booking.

Adds a new comment to a site equipment booking, or edits an existing comment's text when Commands.EquipmentBookingCommentSaveCommand.ItemId matches an existing comment.

Saves the booking-date step of a site equipment booking (booking date, weather info, time slots). Creates a brand-new booking with status UnApproved when none exists yet for the given id, or updates the existing booking's (or draft's) booking info otherwise.

Saves the "other info" step of a site equipment booking (creator/on-site responsible persons, photos, documents, comment). Depending on whether the booking is still being drafted or already exists, this finalizes creation (assigning a booking number and queuing the create-background command) or updates its draft (queuing the update-background command); it also re-validates the calendar slot reservation.

Saves the transport-info step of a site equipment booking (building/floor location, transport unit quantity, recipient team, material comment, price per unit) onto the booking record or its draft.

Queues a background command that sends a "booking requested" reminder email (in every supported language) for a still-open (unapproved) site equipment booking; the command is placed directly on the message queue and this endpoint returns immediately without waiting for the email to be sent.

Updates an existing site equipment booking's booking/transport/other info from the mobile app, re-validating and re-creating the calendar slot reservation, then queues a background command that updates the timeline and sends the relevant status-change notifications.

Activates or deactivates an existing site equipment record by toggling its Active flag.

Transitions a site equipment booking to a new status (e.g. approve, reject, withdraw, cancel, complete), updates its timeline entry, and queues a background command that either completes the linked equipment timeline (calculating actual usage/price and freeing up slots, when completing) or performs the corresponding status-change side effects such as sending notification emails.

Creates a new unplanned equipment usage record attached to a material handover, or updates an existing one's usage/price/slot data. On create it also (re)builds the equipment's timeline entry, assigns a booking number, and logs an event; the same happens for updates.

Saves step 1 of the Smart Shipment wizard: the booking date, lean card and weather/timezone context. If no shipment exists yet for the given ShipmentId, creates a new draft shipment (status UnApproved) linked to the lean card's site; otherwise updates the booking-date fields on the existing shipment (or on its smart-draft, if the shipment is already a valid, non-draft shipment).

Saves step 2 of the Smart Shipment wizard: the selected unloading zone, delivery time slots and the bookable/non-bookable equipment associated with the shipment. Resolves the full zone (and its waiting area, if any) and applies the schedule to the shipment directly, or to its smart-draft if the shipment already exists as a valid (non-draft) shipment.

Saves step 4 of the Smart Shipment wizard: the delivery materials and drop-off details (building, floor, laydown area, recipient team) for the shipment. For a new (drafted) shipment this persists the material lines to the shipment and saves each ShipmentMaterial individually; for an existing shipment it stores the material info on the shipment's smart-draft instead.

Saves the final step of the Smart Shipment wizard: responsible persons, shipment photos/documents, comment and sustainability info, and finalizes the shipment. Validation reserves the unloading-zone timeslot and any bookable/non-bookable equipment via the calendar service (rolling back reservations on failure). On success, promotes the draft/smart-draft into the real shipment: for an update it applies the requested status change (when HasAction is set), refreshes material handovers and updates grouping counts; for a new shipment it assigns a shipment number and updates grouping counts. In both cases a background command describing the change is recorded (as a pending ClmCommand) and sent to the processing queue to actually create/update the shipment downstream.

Saves step 3 of the Smart Shipment wizard: the unloading vehicle details for the shipment's booking date. Applies the vehicle information to the shipment directly, or to its smart-draft if the shipment already exists as a valid (non-draft) shipment.

Validates and completes a site-equipment timeline entry: records the completion amount, optionally frees up any remaining reserved calendar slots for the equipment, updates the related shipment/site-equipment booking, and sends a booking-completed notification email in every supported language.

Queues an asynchronous request to build an Excel export of the site-equipment timeline, filtered by site, status, date range, team/equipment ids and search keys, and returns immediately without waiting for the report to be generated.

Queues an asynchronous request to build an Excel export of the shipment list view (UP timeline), filtered by site, status, schedule date range and sender/recipient teams, and returns immediately without waiting for the report to be generated.

Saves a new "equipment view" cockpit filter (site, recipient teams, bookable/non-bookable equipment and annotation flags) for the current user.

Saves a new "weekly view" cockpit filter (site, sender/recipient teams, moving/unloading equipment and annotation flags) for the current user.

Removes an existing "equipment view" cockpit filter belonging to the current user.

Removes an existing "weekly view" cockpit filter belonging to the current user.

Adds or removes a material from the current user's favorite materials list for a given site.