Robin, inside Claudeyour AI assistant

Changes the time of an existing desk reservation in place — extend it, shorten it, or shift it — keeping the same booking rather than cancelling and rebooking. A booking that has not started keeps its id; one already in progress may be SPLIT by the service into an elapsed part and a new live booking, and the new part does not carry the original check-in (see updatedReservations). Pass only the bound(s) that change; an omitted start or end is kept as is. The new window goes through the same guard as a fresh booking: nothing entirely in the past, a slipped start bumped forward to now and reported. Works on the calling user's own, non-recurring bookings only — someone else's reservation, a recurring series, and an assigned desk are refused with the supported route instead. Performs the write immediately once the reservation and the new time are settled; returns the previous window beside the new one and a ready-made call to put it back.

Discard a stack plan and every floor-split proposal under it. There is no way to discard one proposal on its own. Scenario drafts built from a proposal are not affected. Confirm with the user first — this takes the whole plan.

Attaches a meeting room to an existing calendar event, for the meeting's own window. Only the organizer or someone who can edit the meeting can do this; for anyone else it refuses and says whose meeting it is. This performs the write immediately — settle the room with the user first; suggest_spaces shows what is free. A meeting holds one room: booking the same room onto the same event twice is safe (the second call reports the existing booking), and a meeting that already holds a different room is refused. To swap rooms, add more than one, or set buffers, use update_event: it does it in one call, and if the new room is refused outright nothing changes (a room can still decline afterwards). It never creates, moves or re-times the meeting, and refuses request-only rooms (those are requested in Robin). Undo with cancel_booking.

Removes a desk reservation: cancels it outright when it has not started yet, or ends it at this moment when it is already in progress — one tool for both, and the result says which happened. This is the undo for book_desk. A reservation that is already over is refused, and a recurring booking requires you to say whether the user meant this one occurrence or the whole series — ask them, never assume. Works on the caller's own bookings and, with delegate permission, on someone else's. Returns the removed booking's desk, window, type and visibility, plus a ready-made book_desk call to put it back.

List the workplace analytics metrics available for scenario planning in this organization — one per question: commonly booked rooms by type (space_reservations_count, group by meeting__space_type), rooms consistently under capacity (undersized_meetings_count, group by meeting__space_name), desks used by an individual (desk_checkin_days_count, group by reservation__assignee_name), and desks a team reserves on a typical day (avg_desks_used_per_day: distinct desks reserved per day the group had a booking — reservations including no-shows, not check-ins, averaged over the days the group was in, not over all office days; group by reservation__assignee_department, reservation__assignee_manager_name, or reservation__level_name). Returns each metric’s id, description, allowed group-bys, allowed filters, and date-range behavior. These are the only metrics execute_scenario_planning_metric accepts; always call this first, for the building you will execute against, and use the ids and options it returns. Takes the building_id only; needs planning access to that building.

Execute one of the scenario planning metrics (commonly booked rooms by type, rooms consistently under capacity, desks used by an individual, desks a team reserves on a typical day) for one building and return the result (a single value, or grouped rows when group_by is given) with the applied date range, filters, and provenance. The building is a filter in the query itself, so results cover only that building and building_id is echoed on the response; do not add the building to group_by. For how many desks a team reserves on a typical day, use avg_desks_used_per_day grouped by the lens you need (department, manager, or level) and say it counts reservations including no-shows, averaged over the days the group was in. It has a different basis from desk_checkin_days_count, which counts check-in days per person; do not present one as the other. Needs planning permission on the building, or collaborator access to one of its drafts or stack plans: viewers are refused (viewer_only), others too (no_planning_access), and collaborators may group and filter by place and time only, never by anything that names a person (aggregates_only, with the allowed dimensions in valid) — relay these in plain words and do not retry. A truncated result (truncated: true) was capped within the building, like any other grouped result; say so rather than retrying. Use find_scenario_planning_metric first for the metric ids and their allowed group-bys and filters; no other metric id is accepted. Validation failures return a structured error with the valid options — correct the arguments and retry.

Invite people to a building draft as collaborators or viewers, so they can review or help build a plan before it is published. This NOTIFIES the people invited: invite only who the user named, and only when they asked for it. Requires an explicit accessLevel — 'collaborator' can change the draft, 'viewer' can only read it, and NEITHER can publish it: that stays with the draft's owner. Takes NO version: sharing is outside the draft's version chain, so there is nothing to chain here. First check who already has access — get_draft (include collaborators), or for a stack plan get_stack_plan (include collaborators) — since re-inviting someone emails them a second time for nothing.

Find people, desks, spaces, or bookable resources in the caller's organization by name or email. Returns matching entities with their IDs, types, and location context, for use as inputs to other tools. Optionally restrict to specific entity types; omit entityTypes to search everything.

Pre-flight a desk booking: for up to 100 desks and up to 30 time windows (at most 750 desk-window pairs per call), report each desk's availability status per window, the typed reasons it cannot be booked (policy violations, access, capacity — each carrying the rule's value and a plain-language explanation, so a rejection contains the rule it broke), the reservations occupying it, and any exclusion windows (released assigned desks — bookable as reverse_hotel when the window fits entirely inside one). For a multi-day or recurring plan, pass each day's span as its own window in ONE call instead of calling once per day. This answers whether SPECIFIC desks can be booked; it is not a floor sweep — narrow the desks first (find_desks by floor or zone) and bring their ids here. Availability is evaluated for the calling user unless userId is given, and each desk reports bookedByRequestingUser — the flag that separates a desk someone ELSE holds from one the evaluated user already holds themselves (private bookings included, also when checking on someone else's behalf), the latter being reschedulable in place even though the desk reads as not bookable. Assigned desks (types ["assigned","shared"]) are judged the way the office map judges them: bookable only as reverse_hotel on a day the assignee has released the desk — releasedForWindow, assignees, and bookAs report exactly that, and bookable already folds it in, so an unreleased assigned desk nobody sits at reads status AVAILABLE but bookable false. Zone-less window bounds are read in timeZone when given (pass the same value to book_desk), else the caller's timezone. ALWAYS check the chosen desk here before book_desk: booking rejections that this surfaces in advance include conflicts, advance-booking limits, max length, working hours, and floor capacity — and capacity is only enforced here, not at booking time.

List every office location (building) in the caller's organization, with address and timezone. The id of each is the buildingId the building tools take. For a building's size and shape — floors, desk counts by booking type, neighborhoods — pass it to get_building. When only the floor ids and names are needed, get_location_levels is the one cheaper call.

No parameters required.

Reads one meeting by event id: its time, attendees, rooms, check-in, and what the caller is allowed to do to it (permissions). Read it before proposing any change or cancel, and only propose what permissions allows. Get the event id from list_calendar_events.

Books a desk for a settled desk and time window, and returns everything needed to report the booking back and offer an undo. Books for the current user by default, or for another person when forUser (their email) is given — which requires delegate permission. This tool performs the write immediately; confirm the desk, window, and reservation type first (check_desk_availability shows what is bookable and which reservationType to send as bookAs). It does not re-check availability itself, but the window goes through the same guard as the read tools: start and end may carry an offset or be zone-less (then read in timeZone, the request timezone, or the caller's profile timezone, in that order), a window that has already ended is refused, and a start that has merely passed is clamped to now and reported as effectiveStartTime. Assigned desks follow their own rule: one is bookable only as reverse_hotel, and only on a day its assignee has released it — with no release (or no assignee to release it) it is seated by an admin assignment instead and cannot be booked by anyone.

Buildings and floors in one call. No buildingId: every building with id, address and timezone. With one: the building and its floors (levelId, desk count). include adds overview (active desks per floor by booking type), neighborhoods (colour slot, membership), neighborhoodColors (the slots update_draft accepts) and desks (booking types and who sits at each desk; planners only, 4 floors per call, narrow with levelIds). assignees: where those people sit (planners only). All live; no draft needed.

Answer "what desks are free on floor X for this window" in one call: sweeps an entire level for a time window and returns the desks that are bookable by the calling user (with names, booking types, pod, amenities, and the reservationType to book them as), plus how many are busy or off-limits. Assigned desks follow the office map's rule: one is listed only when its assignee has released it for the window (then with bookAs reverse_hotel) — the rest are counted in assignedNotBookableCount. Optionally filter to desks with specific amenities — call once without deskAmenityIds to get the floor's amenity ids from levelDeskAmenities, then re-call with them. Use this instead of paging find_desks results through check_desk_availability in batches. A window that has already ended is refused; a start that has merely passed is clamped to now and reported as effectiveStartTime, which then replaces the requested start everywhere. Availability reflects the caller's own access and conflicts; still call check_desk_availability on the desk you pick before book_desk, since policy limits and floor capacity are only reported there.

List a user's desk reservations within a time range: which desk (with its floor and building names), when, the reservation type, check-in state, and who booked it, sorted earliest-first. Omit userId for the calling user (it resolves automatically); resolve anyone else with search_entities. Times are ISO 8601 datetimes; use the start and end of the user's day (in their timezone) to answer questions about a specific day. For preference questions ("my usual desk", "which days am I normally in", "how often do I come in"), query a past range (4-8 weeks works well) and read the server-computed `analytics` block instead of counting reservations yourself.

Read one floor's draft state: its desks (booking types, who the draft seats there) and neighborhoods (name, colour slot, desk membership), each flagged if it differs from the live plan, plus the draft's version. levelId is required; one floor per call. Not a pure read: it creates the floor's child draft on first call and syncs newly added seats, which is right after create_building_draft; repeating it changes nothing. With no draft in play, use get_building with include neighborhoods.

The building's working day, date by date: opening time frames for a range of calendar dates, with closed days (weekends, holidays, closures) coming back as empty. Use it to propose real booking hours instead of assuming 9:00–17:00, and to skip closed days when planning multi-day bookings — a day with open=false should never be booked. locationId defaults to the calling user's default building; all times are local wall-clock times in the building's own timezone (returned alongside).

Cancels a meeting the caller organizes (or may cancel as a delegate) for EVERYONE: it is removed from every attendee's calendar and its rooms are released. Cannot be undone; confirm with the user first. For a recurring meeting, pass scope with the user's answer to 'just this one, this and following, or the whole series?' — the call is refused without it. To take a room off a meeting while the meeting goes on, use cancel_booking instead. After success, tell the user which scope was cancelled.

Find people and return the user ids the draft tools take, each with their default building. Filters AND together: userNameFilter (a PREFIX of name, surname, slug or email), departments (exact strings; include departments lists them with headcounts, so never guess one), managerIds (direct reports; ids, not names; include managers lists them), reportsOf (a manager's whole chain at every depth; combine only with departments), addedWithinDays, statuses (omit to exclude deactivated people). With buildingDraftId each person carries their access to it; add assignmentStatus UNASSIGNED for who still has no desk in it. accountUsersTotal is the full count, not the page: state it before seating a group.

Saved stack plans for a building — proposals, not current seating (read that with get_building (include desks)). No stackPlanId: list the building's saved plans (buildingId required), names and descriptions only. With one: the plan in full — its business-unit variations, every floor split with each floor's capacity against what it places there, what each split leaves short, and the building drafts derived from each; include collaborators adds who the plan is shared with. Read-only.

Read one building draft without changing it. Always returns its version (what the write tools take), its status and the link that opens it in Robin. assignees adds where those people sit with the draft's changes applied. include adds review (what publishing would change per floor, with the bookings it would cancel), collaborators (who it is shared with, at what level) and queue (who waits for a desk on levelId). Takes create_building_draft's buildingDraftId. Floor desks are get_draft_data.

Read the matching guide FIRST, before create_building_draft, update_draft, publish_draft or any stack-plan tool. stack_planning covers how teams are seated across a building today, consolidation and what-if layouts; scenario_planning covers seating or moving people, changing desks and neighborhoods, and publishing a draft. Returns which tool to call in which order, the draft lifecycle rules, and how to talk to the user while planning.

Moves a meeting to a different room when the meeting lives on a room's calendar: its organizer room (get_event marks it isOrganizer). For any other room on a meeting, add, remove or swap it with update_event instead. Find the room with search_entities when the user names one; to offer replacement rooms, use suggest_spaces' windows form with the meeting's start and end, and its attendeeCount as capacity. Confirm the room with the user before calling. Keeps the meeting's time; to change the time, use update_event. A recurring meeting moves this occurrence only. Attendees are notified unless the user says not to. The move is submitted, not finished: tell the user it is on its way, and before changing the meeting further, find it again with list_calendar_events (on Microsoft it gets a new id). Never show ids to the user.

Creates a NEW meeting on the user's calendar, optionally with rooms and people. For a meeting that already exists, add a room with book_space instead. Resolve names first with search_entities (people and rooms). When several rooms match, ask the user which, naming each one's building and floor — the meeting may be for someone else, somewhere else. Then confirm everything with the user in one message — time and zone, rooms, people, and anything you assumed — before calling: this books immediately. Request-only rooms and repeating meetings are refused. A meeting with no room needs a personal calendar Robin can book on; if there is none, the result says so — then ask the user for a room. If a room is taken, follow the returned guidance; do not try rooms one after another.

Changes an existing meeting for everyone on it: title, description, time, people, rooms and room buffers, or recurrence, in one call. Send only the changes the user asked for, as commands in `changes`. Resolve people and rooms by name with search_entities first; ask when a name matches several. A time without timeZone is read in the meeting's own zone. To swap a room, remove the old one and add the new one in the same call: if the new room is refused outright, nothing changes, but a room can still decline afterwards, so check with get_event before telling the user it is confirmed. The room the meeting itself lives on cannot be removed here. For a recurring meeting, pass scope with the user's answer to 'just this one, this and following, or the whole series?' — the call is refused without it. Confirm the change with the user before calling: dryRun: true reports exactly what the call would do, side effects included, without changing anything. Never show ids to the user.

Apply changes to a building draft in one batch, under its optimistic lock: DESK changes (reservability, reservation types, assignments), NEIGHBORHOOD changes (name, colour slot, desk membership, create and remove) and QUEUE changes (add or remove people on a floor's waiting list). Takes create_building_draft's buildingDraftId and the draft's current version; returns the new version for the next update_draft or publish_draft. Before a neighborhood change read get_building (include neighborhoodColors: a colour is a named slot, not a hex) and get_draft_data (membership REPLACES what is there). Seating a queued person does not dequeue them: send a QUEUE remove for them in the same batch.

Save a stack plan for a building along with the business-unit options it is weighing. Each option is a set of building-wide desk totals per business unit. Returns the plan id and an id per option, which update_stack_plan set_allocation needs to propose a floor split.

PUBLISHES a building draft to the LIVE floor plan: irreversible and visible to the whole workplace. Before calling, read get_draft (include review) and confirm with the user. Takes the draft's current version (from the latest update_draft) and the numeric levelIds to publish. EMAIL: the publisher always receives a summary and that cannot be turned off; every other email is off unless the user asked for it. sendNotifications emails the people affected (changed assignments and cancelled reservations, together); exportCSVUserIds emails a CSV of the changes to the recipients named. Publishing is ASYNCHRONOUS: a successful return means the publish was ACCEPTED. Pass waitSeconds (up to 30) to wait for it to settle and get the final status back; if it is still publishing after that, confirm later with get_draft. Never retry this tool or create another draft while a publish is in flight.

Start a floor-plan draft for a building. Returns the buildingDraftId that every subsequent lifecycle call (update_draft, get_draft, publish_draft) requires — child floorDraftIds are never valid there. The new draft starts at version 0.

Get an office location (building) by ID with its address and timezone, plus every floor with that floor's total desk count. Use it to resolve a floor name to the numeric levelId the draft tools take. deskCount includes inactive desks — to see individual desks, their booking types, and who sits on them, use find_desks with that levelId. For desk counts by booking type across floors, or each floor's neighborhoods, use get_building instead.

Resolve a desk reference like "Pod 1, Desk 2" to desk ids (deskName, optional podName and levelId; exact matches first, and if several match, ask the user), or omit deskName and pass levelId to list every desk on a floor with booking types and assignee count: an open assignable desk is deskTypes ["assigned","shared"] with assigneeCount 0. Reads the LIVE floor plan; for a floor as the draft would leave it use get_draft_data, and for desk counts alone use get_building (include overview).

The calling user's identity and context in one call: userId, name, email, timezone, organization, default building (defaultLocationId) and floor (defaultLevelId), and currentDateTime, the authoritative current instant. Takes no input. Call it FIRST for any request about the user themselves ("my desk", "my building") and for any relative date ("today", "next Tuesday"): resolve the date against currentDateTime in the user's timezone, because a booking in the past is accepted silently.

No parameters required.

Change a stack plan after create_stack_plan. action add_variation records one more set of building-wide desk totals on the plan: a variation freezes once a split implements it, so a revision is a new variation, not an edit or a second plan. action set_allocation proposes how a variation's desks sit across floors: with variationId and name it creates a split; with allocationId and the version last read it rewrites the floors sent (each replaces that floor outright, floors left out stay) or renames it. Returns what the split still leaves short against its variation (shortfalls, reported not refused) and each written floor against its real desk count. get_stack_plan reads it all back.

List the calling user's calendar events for a date, or a range of up to 14 days, with each event's headcount and whether it already has a space booked. Call this first for any request that names a meeting ("my 10am tomorrow", "Thursday's standup") — the eventId it returns is what suggest_spaces and book_space take. With withSpace: true it lists only the meetings on the caller's calendar that hold a room — there is no separate bookings tool — each with the spaceId that cancel_booking takes. Reads only the caller's own calendar, and refuses when no calendar is connected, so an empty list means free days (or, with withSpace, no room held).

Draw a stack plan: one row per floor, every desk as a chip coloured by its group, with a legend. Use it for questions about a WHOLE building — how space divides across floors, where there is room, whether a team is split up — and to show a PROPOSED layout before anything is written to Robin. You supply the rows, so read the building first (get_building for the floors, then get_building with desks included for who sits where today, or get_draft_data per floor for a draft, joined to find_people for departments and managers) and pass the counts you worked out. Send the same numbers you describe in prose. Do not call this on a vague request: confirm which building and which breakdown first, since reading a building is many calls.