Jibble

Deletes a list of schedules by their IDs. Use get_all_schedules to get schedule IDs if not known. Maximum 6 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

delete_schedules

Ends an in-progress break for a person. The backend creates a clock-in (In) TE that resumes work, automatically restoring the project and activity from the clock-in entry before the break. Completes the flow started by 'start_break'. Supports ending a break at a specific past time using the time parameter. Future scheduling is not supported. To find the most suitable location, use 'get_all_locations' tool. To see who is currently on break, use 'get_who_on_break' tool. MANDATORY: Always call this tool when a user requests to end a break or resume work after a break, regardless of previous conversation history or perceived status. This tool is the ONLY source of truth for the user's current break state. If the person is not on break, the backend returns an error (e.g., 'Invalid operation, nothing to end'), which you must then report. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

end_break

Use this tool when the user asks a question related to the Jibble API. It returns a list of API documentation that provides technical context, guidance, and reference information about Jibble's API endpoints. IMPORTANT for multilingual users: If the user asks in another language, translate the API question to English before calling this tool, then explain the answer back in the user's original language. This tool is ideal for retrieving relevant API documentation and technical specifications that can help the user understand how to integrate with and use the Jibble API effectively. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_api_docs

Returns a geofence compliance dashboard for a person or group over a date range. Reports clock-in/out entries that the backend flagged as outside the assigned geofence. Counts flagged and not-flagged entries. The flag does not establish GPS availability or actual compliance: entries without GPS can be unflagged. Date boundaries are UTC; occurrence times retain recorded offsets. Provide either PersonId or GroupId. When PersonId is provided, it is used directly and GroupId is ignored. Date range defaults to the last 30 days when omitted. Use for queries like 'Who clocked in outside their geofence?', 'Show geofence violations this week', 'Geofence compliance for the sales team'. Max 30-day range to keep query cost bounded for large groups. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request. When the widget is displayed, give only a brief summary without repeating its table or rows, unless the user explicitly requests a text table. If no widget is displayed, answer using the tool results.

get_geofence_compliance_dashboard

Use when users ask how to navigate to/find Jibble pages or features. Returns role-filtered routes with URLs. For multilingual queries: infer/translate the navigation intent to English when matching feature names and route keywords, but keep URLs unchanged and reply to the user in their original language. CRITICAL: Only provide complete, functional URLs with all data filled in. NEVER show templates, placeholders (:id, {param}, YYYY-MM-DD), or URL patterns. If parameters missing: State what's needed, wait for data, then show complete URL only. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_app_ui_navigations

Returns punctuality and attendance analytics for specified people within a date range: attendance score (0-100, percent of scheduled work days the person showed up), counts of on-time / late / no-show / rest days, average first clock-in time, average last clock-out time, and average break duration. Use this tool when the user asks about punctuality, lateness, absenteeism, no-shows, attendance scores, or average start/end times. For observed earliest/latest first clock-ins or their distribution, use get_clock_in_patterns when listed. 'PersonIds' is optional: leave it out to cover everyone the caller can see (admins/owners: the whole organization; managers: their managed people). Without 'GroupBy' that is one page of people per call, so use 'Page' to walk through a large workspace; with 'GroupBy' the whole visible population is aggregated at once and the call fails with guidance when it exceeds 150 people. If the user asked about specific people, resolve the person IDs via 'get_managed_people' first; for a whole team/group, resolve member IDs via 'get_group_persons' first and pass them all. At most 150 person IDs can be passed in one call. Set 'GroupBy' to 'Group', 'Position', or 'Location' to get aggregated rows per group/position/location (each with its member breakdown in 'Members'); leave it unset (or 'None') for one row per person. Dates use yyyy-MM-dd format (e.g., '2026-06-01'); both StartDate and EndDate are inclusive, and the period cannot cover more than 30 calendar dates (e.g. 2026-06-01 to 2026-06-30) — split a longer question into consecutive ranges of at most 30 dates rather than asking for one wide range. Times returned (average clock in/out) are in each person's own timezone context as recorded by the backend. Set 'IncludeDailyStatuses' to true only when the user asks which specific days a person was absent/late — it adds a per-day status list and makes the response much larger. NOTE: late-arrival detection depends on assigned schedules; people without schedule data are only classified as present or no-show. For worked-hours totals use 'get_timesheets'. For a group attendance board, use 'get_team_schedule_view' when listed; for plain live presence, use the listed 'get_who_clocked_in', 'get_who_clocked_out' or 'get_who_on_break' tool matching the requested status. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_attendance_insights

Returns a paginated list of people (personId, personName, positionId, positionName, email, phoneNumber, code, role, status) from a specific group, along with the total count. Supports search by fullName, email, phoneNumber, code, positionId. If user provides a position name, first use get_all_positions to resolve the matching positionId. Use filterMode='Any' (default, OR) or 'All' (AND) to combine multiple search fields. To find group by group name, use 'get_all_groups' tool This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_group_persons

Returns list of all settings used for specific group. Use get_settings_info tool to retrieve settings names, descriptions and value types. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_group_settings

Returns a paginated list of all time-offs requested by persons from specified groups for specified period This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_time_off_requests_for_groups

Returns timesheets summary for ALL persons from specified groups within a custom date range. Use this method ONLY when the user specifically wants to filter by groups/teams. Result will include summary timesheet for each person and a set of daily timesheets. Days with no tracked time are excluded from the response. Fields with zero values are omitted from the response. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_timesheets_for_groups

Gets leave balance as of a specific date, with optional filtering by leave policy and person. Always pass requestDate; when the user gives no date, use today's date and state it in the answer. For specific leave types, resolve the policy via get_all_time_off_policies and pass policyId. Omitting personId applies no person filter: for the caller's own balance, pass their person ID (get_person_assignments with no person returns it when listed). Resolve person names via get_managed_people when listed. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_leave_balance

Returns a person's comprehensive time-off history in a requested date range to EXPLAIN balance differences, policy assignments, administrative actions, and leave-related changes. The AGENT SHOULD: fetch entries; analyze by date range, CalculationType, and administrative actions; identify who performed actions and when; sum changes by type; and provide detailed explanations for balance discrepancies, policy changes, and administrative history. BOTH START DATE AND END DATE ARE REQUIRED. Use it to explain one person's leave balance changes; do not use it to assemble a team report. For everyone's current balances, call get_leave_balance without a person. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_leave_history

Returns a paginated list of people (personName, personId, positionId, positionName, email, phoneNumber, code, role, status) that the current person can act on behalf of, along with the total count. Supports search by fullName, email, phoneNumber, code, positionId. If user provides a position name, first use get_all_positions to resolve the matching positionId. Use filterMode='Any' (default, OR) or 'All' (AND) to combine multiple search fields. When any search filter is provided, returns people regardless of status. For managers - manageable via group or directly. For Admins/Owners - all people. For others - only themselves This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_managed_people

Returns list of all settings and exact values used in the organization. Use get_settings_info tool to retrieve full settings list with settings names, descriptions and value types. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_organization_settings

Returns a paginated list of people (personId, personName, email, phoneNumber, code, role, status, timeSheetTimeZone) assigned to a specific schedule. Use 'get_all_schedules' to find schedule IDs by name or work arrangement type. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_people_by_schedule

Returns everything a person can track time against, in one call: assigned activities, assigned projects, effective work schedule, upcoming holidays, and geofenced locations (allowed clock-in areas). Use this before clock_in or add_hour_entries to resolve valid activity/project IDs for a person, or to answer questions like 'what can I clock in to?', 'what is my schedule?', 'where am I allowed to clock in?'. If otherPersonId is omitted, returns assignments for the current person. If only a person name was provided, resolve the GUID via get_managed_people when listed. Sections that fail to load are reported in sectionErrors without failing the whole call. For full break/overtime/auto-deduction details use get_user_settings; for org-wide lists use get_all_activities / get_all_projects. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_person_assignments

Gets a calendar (e.g., public holidays). If otherPersonId is provided, filters by that person. If only a person name is provided, resolve it via get_managed_people when listed; otherwise, use the current person. When no holiday calendar is configured, returns a successful empty result with IsConfigured=false; do not retry unless calendar configuration changes. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_public_holidays

Returns a list of all settings can be configured for Organization in Jibble with detailed information about each setting. Use this tool to provide more detailed information about settings in additional to the information from help articles. This tool can be used to answer user's questions related to settings, such as: 'Which settings can be configured for Organization?', 'Which settings are configurable for Organization?', 'What is the default value/possible values for setting X?'. Also it can be used to build an input for update_organization_settings when that tool is listed. Each setting property includes 'restrictions' indicating which subscription plans restrict that setting and how. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_settings_info

Returns the calling organization's current subscription plan, its effective feature restrictions and limits (including any organization-level overrides), and the full catalogue of subscription tiers with the restrictions imposed by each tier. Use this tool for any question about plans, subscriptions, features, feature availability, or feature limits/quotas. Call it BEFORE searching help articles for these topics — this tool is authoritative for the caller's actual plan and limits, whereas help articles describe the product generically and do NOT reflect the caller's actual entitlements. Feature identity for comparison/explanation is the (Code, Type) pair on each restriction row — use these stable codes when explaining which tier unlocks a feature. For entitlement actions such as starting a feature trial, use the restriction's FeatureIds (the product-feature GUIDs) as the feature identifier — never the Code or display name. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_subscription_feature_catalogue

Returns raw clock-in, clock-out, and break records, newest first. Omit person selectors for yourself, use OtherPersonId for one person, or PersonIds for up to 100 people within your permitted scope. PersonIds requires StartDate and EndDate (yyyy-MM-dd), inclusive UTC days, covering at most 31 days inclusive; the dates also work with a single person. They are UTC days, not timesheet-local: for a local calendar day, widen the range by one day on each side and keep the entries whose timestamp (local time) falls on that day. Each page covers the entire selected population; read pages sequentially. For worked-hours totals or daily summaries, use get_timesheets instead of calling this once per person. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. Maximum 100 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

get_time_entries

Returns raw time-off request records (dates, status, duration, policy) for a period as paginated JSON. Use this tool for the caller's own requests and for raw records needed for a calculation or export. To display or review other people's requests, use get_time_off_requests_view when listed; otherwise use this tool. Omitting PersonIds applies no person filter: for the caller's own requests, pass their person ID (get_person_assignments with no person returns it when listed). Resolve person names via get_managed_people when listed. For detailed leave history including balance changes, policy assignments, administrative actions, and explanations of balance discrepancies, use the get_leave_history tool instead. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_time_off_requests

Retrieves time tracking data with flexible grouping and filtering. Use this tool when the user asks about hours spent, time allocation, usage patterns, or comparisons for projects, clients, or activities. This includes queries like: 'How many hours for Project X?', 'Most/least used project', 'Top N projects/activities/clients by hours', 'Projects with no tracked time', 'Highest billable amount', 'Compare Project A vs B', or 'Resource allocation analysis'. IMPORTANT: The tool requires specific start and end dates (yyyy-MM-dd format). For relative periods like 'last week', 'this month' or 'this quarter', compute the range and state it in the answer. For 'all time', ask for a start date. Set GroupBy to 'Project' for project analysis, 'Client' for client analysis, or 'Activity' for activity-based reports. Use ProjectIds, ClientIds, or ActivityIds to filter specific entities (resolve names to GUIDs using get_all_projects, get_all_clients, or get_all_activities first). Returns aggregated time entries grouped by the specified dimension with detailed breakdowns including total hours, daily items, and billable information. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_time_tracking_report

Returns the timesheet time zone for a person. If anotherPersonId is provided, fetch it for that person. If only a name was supplied, resolve the GUID via get_managed_people when listed. If neither is given, return the time zone for the current person. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_user_time_sheet_time_zone

Returns timesheets summary for specified persons within a custom date range. Use this for worked-hours totals and daily timesheet summaries; for a grouped or ranked hours dashboard, use get_team_time_insights when listed. You can optionally filter by specific person IDs. Resolve person names via get_managed_people when listed. Result will include summary timesheet for each person and a set of daily timesheets. Days with no tracked time are excluded from the response. Fields with zero values are omitted from the response. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_timesheets

Returns all settings affecting clock-in, clock-out, and break flows. If anotherPersonId is provided, fetch settings for that person. If only a name was supplied, resolve the GUID via get_managed_people when listed. If neither is given, return the settings for the current person. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_user_settings

Returns the full wizard definition with all steps for a given wizard ID. Use this tool after calling 'get_wizards' to retrieve the complete step-by-step instructions for a specific wizard. Follow the steps in order to answer the user's question. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_wizard

Returns a leave utilization dashboard showing how much of their entitled leave each person has used. Helps identify people with excess balance or high usage. Use for queries like 'Show leave utilization', 'Who has unused leave?', 'Team leave balance overview'. Optional GroupIds to filter by team. Optional Date for as-of balance (defaults to today). This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request. When the widget is displayed, give only a brief summary without repeating its table or rows, unless the user explicitly requests a text table. If no widget is displayed, answer using the tool results.

get_leave_utilization

Returns a paginated list of activities (activityName, activityId, activityCode) available for person. By default returns only Active activities. Use status parameter to filter by specific status or get all. Use code parameter to filter by activity code. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_activities

Returns a paginated list of clients (clientId, clientName, clientCode) available for the person. By default returns only Active clients. Use status parameter to filter by specific status or get all. Use code parameter to filter by client code. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_clients

Returns a paginated list of groups (groupId, groupName) available to a person (all groups from organization, managed group for manager). By default returns only Active groups. Use status parameter to filter by specific status or get all. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_groups

Returns a paginated list of locations (locationName, locationId), available for person. By default returns only Active locations. Use status parameter to filter by specific status or get all. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_locations

Returns a paginated list of positions (positionId, positionName) available for the person. By default returns only Active positions. Use status parameter to filter by specific status or get all. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_positions

Returns a paginated list of projects (projectName, projectId, projectCode) available for person. By default returns only Active projects. Use status parameter to filter by specific status or get all. Use code parameter to filter by project code. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_projects

Returns a paginated list of schedules (scheduleName, scheduleId, workArrangement, weeklyHours, daySchedules) available for person. For Fixed arrangements, daySchedules carries from/to per day. For Flexible arrangements, daySchedules carries duration per day. For Weekly arrangements, weeklyHours is set and daySchedules is null. Optionally filter by specific person, group, or work arrangement type (Fixed, Flexible, Weekly). Use get_managed_people to resolve person names to IDs, or get_all_groups to resolve group names to IDs. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 250). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_schedules

Returns a paginated list of time-off policies. By default returns only Active policies. Use status parameter to filter by specific status or get all. If the user asks about a policy's details (e.g., accrual rules, compensation type, balance rules), the agent SHOULD use the detailed description of each property in the Policy and AccrualSettings models. This tool supports pagination. Use the 'PageSize' parameter to control the number of items returned per page (maximum: 100). Use the 'Page' parameter to request a specific page of results (1-indexed). The response includes: 'TotalCount' (total items), 'Page' (current page), 'PageSize' (items per page), 'TotalPages' (total pages), and 'ReturnedCount' (items in this response). To retrieve only counts without data, set 'PageSize' to 0. This tool does not support batching for write operations. Repeated calls are allowed only for pagination/reading pages; do NOT use multiple calls to bypass operation limits for a single user request.

get_all_time_off_policies

Returns a list of available guided workflows (wizards) that help answer complex questions requiring multiple steps. Use this tool when the user asks a complex or unclear question that may require calling multiple tools in sequence, analyzing intermediate results, or combining data from different sources. Each wizard provides a structured, step-by-step plan for the AI to follow. After finding a relevant wizard, use 'get_wizard' to retrieve the full step-by-step instructions. This tool does not support batching. Do NOT call this tool multiple times automatically to fulfill one user request. If the user asks for repeated actions with this tool, ask them to split and send separate requests.

get_wizards

Manage activities by updating, archiving, or unarchiving them in batch. Use get_all_activities to retrieve activity IDs. To clear optional fields: use '__CLEAR__' for string. Maximum 6 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

manage_activities

Manage group assignments for activities. Use get_all_activities to retrieve activity IDs and get_all_groups to retrieve group IDs. Can add groups, remove groups, or replace all groups for an activity. Maximum 6 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

manage_activity_group_assignment

Manages groups in batch: create, rename, archive/unarchive groups, move people in or out of groups, and set group managers and pay-period approvers (first/second level). Provide at least one of the operation lists. Operations are processed in this order: addGroups, renames, archiveGroupIds, unarchiveGroupIds, memberAssignments, setManagers, setFirstApprovers, setSecondApprovers. Use get_all_groups to resolve group names to IDs and get_managed_people to resolve person names to IDs. A person can belong to only ONE group — assigning a member to a group moves them out of their previous group. Use groupId '11111111-1111-1111-1111-111111111111' in memberAssignments to remove a person from their group. Managers and approvers are replaced as a whole set per group: by default assignPersonIds are merged with the existing set and unassignPersonIds removed; set replaceAll=true to overwrite the set with exactly assignPersonIds. Archiving a group does not archive its members. New groups inherit organization-level settings automatically. Maximum 6 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

manage_groups

Manages workspace members in batch: invite new people, update profiles (name, email, phone, code, group, position, employment type, work start date), change roles, archive or restore members, resend pending invitations, and reset kiosk PINs. Provide at least one of the operation lists. Operations are processed in this order: invites, updates, setRoles, archivePersonIds, restorePersonIds, resendInvitationPersonIds, resetPins. Use get_managed_people to resolve person names to IDs, get_all_groups for group IDs, and get_all_positions for position IDs. Role changes accept Member|Manager|Admin only — ownership transfer is NOT supported and must be done in the Jibble web app. Email and phone number of a person who has already accepted their invite CANNOT be changed (only that person can change them in their own account). Archiving sets the member status to Removed (the Jibble UI shows this as an archived member); it does not delete any data and can be undone with restorePersonIds. To clear optional string fields in updates use '__CLEAR__'; to clear group/position/employment type use '11111111-1111-1111-1111-111111111111'. MANDATORY: before archiving or resetting PINs, confirm the exact person with the user if multiple people match a provided name. Maximum 6 items are allowed across array inputs in a single call. Do NOT bypass this by making multiple tool calls automatically. If the user provides more than this limit, ask the user to narrow the request first.

manage_people