Your GeoDynamics data, right inside your AI assistant

No input. Returns companies, each with companyId, companyName and isDefault (the company picked at sign-in). Every other tool takes one of these as an optional companyId; without it, the tool reads the default company.

Start here: the id it returns is the userId that getTimesheetSummary takes.

Returns items, total, page, pageSize and hasMore. Each user has id, name, code, dayProgramId and mobilityRule (the name of the mobility scale, or null). Names are not unique: tell people apart by id.

From V5's timesheet reconstruction: worked hours, breaks, absences and overtime per day and for the period, the same numbers as the timesheet. For hours per activity or cost center, use the post-calculation tools below.

Returns one row per day and the period totals, every duration in decimal hours: normalHours, grossWorkHours (break included), breakHours, netWorkHours, paid and unpaid absence, loadHours, mobilityHours, mobilityKm and movementKm (distance driven), overtimeHours, undertimeHours and balanceHours. Overtime and undertime are counted per day, so a period's overtime is not offset by its undertime; the balance is. A day without normal time, such as a weekend, has no overtime: its hours only count in the balance. Mobility hours are the fixed amount the mobility rule grants, not measured driving time.

Returns items, total, page, pageSize and hasMore. Each vehicle has id, name, code, unitId (the tracking device) and deviceType.

The places clockings and vehicle movements are matched against.

Returns items, total, page, pageSize and hasMore. Each location has id, name, code, typeName, street, city, latitude and longitude.

Shows active cost centers only, unless you ask for expired ones too. A cost center without an expiration date never expires.

Returns items, total, page, pageSize and hasMore. Each item has id, name, code, expirationDate, active, poi, autoCreate and creationDate, sorted by name, then code.

From V5 post-calculation (nacalculatie): the hours V5 books per activity. For the whole company or one person, optionally split per person.

Returns totalHours and a page of totals (with totalCount, page, pageSize and hasMore), one row per activity (and person) with hours, normalWorkedHours, overtimeHours and days, largest first. hours also splits into workHours, directTravelHours, indirectTravelHours, indirectMobilityHours, loadUnloadHours and indirectAbsenceHours. An absence total carries absenceCode and absenceName; totals without hours are left out. If the company books no activities, the tool says so. days counts person-days: a total for the whole company counts every person's day with hours on it, a total for one person counts that person's days. A closed week is cached for a day, one that reaches today for ten minutes.

Same as getHoursPerActivity, grouped by cost center. Each total also carries fullCode, the cost center as V5 stores it; code is what the company's code pattern keeps of it, so two totals can share a code. fullCode matches code in listCostCenters, ignoring case. Absences sit on the absence cost center, told apart by absenceCode.

Returns the same shape as getHoursPerActivity, with the cost center code as code.

The GeoDynamics fleet reports the signed-in user may run, filtered on their own V5 privileges. Five reports: Maintenance (next service per vehicle by date, km and hours), Mileage per vehicle per month, Mileage per vehicle per day, Export vehicle counters (km or machine hours per vehicle) and Vehicle overview (the fleet register: plate, VIN, fuel type, cost center). None of them contains clockings, positions, addresses or drivers.

Takes no input. Returns every report with its reportKey and what a run needs: vehicle (required or optional), period (day, month or none) and counters with their options.

Runs one report for one vehicle and one day or month and answers with its data as JSON, not as a file, so the agent reads the figures itself. Maintenance can run without a vehicle to check the whole fleet, and then returns only the tasks that are overdue or due soon. When the user has not said which vehicle, day or month, the agent asks first. Costs 5 of the 60 calls per minute.

Returns the report data as JSON: for Maintenance a list of tasks per vehicle with their status (overdue, warning or ok), for the other reports its sheets with one row per line.