ROCKEYE TMS

Resolve valid expense categories for the specified entity_type and return the canonical expense_master_id to be used by create_expense/update_expense. MANDATORY — call this before every create_expense call, with no exceptions. expense_master_id is a category identifier, not a monetary value, a date, or any other number supplied by the user. It must never be copied, guessed, derived, or reused from any other field in the request. The only legal source for expense_master_id is the id field in this tool's response. If the user has already named a category (e.g. \"electricity\", \"fuel\", \"driver payment\"), call with expense_filter set to that term and use the single matching expense_master_id from the result. If no unambiguous match is returned, do not guess — ask the user to pick from the returned list. If the user has not named a category, call with entity_type only, show the returned list to the user, and wait for their selection before proceeding. (Category: Expense Management)

View maintenance analytics for a truck or vehicle. Use when the user asks: - how many days a truck/vehicle is in maintenance - total maintenance days - how many days was a truck under maintenance - maintenance duration or summary or statistics - vehicle maintenance analytics - longest serving maintenance vehicle Requires resolve_entity(entity=truck) first when a truck plate number, truck code, or vehicle reference is provided. RULES: - Use for maintenance counts, maintenance days, and maintenance duration only. - Do NOT use for maintenance history, service logs, repair records, or detailed maintenance entries. - Always resolve the truck before calling this tool when a truck reference is provided. - Never expose internal IDs. OUTPUT: Returns summarized maintenance analytics including: - Total maintenance days or maintenance duration Does not return detailed maintenance log records. Only return number of days truck has been into maintenance. (Category: Truck Operations)