Fleetoo

List the groupings a given metric supports, and every filter it accepts with the filter key, its type, and whether ids must come from resolve_entity first.

List this company's saved reports.

Re-present the result of the most recent run_query in this conversation — a different chart type, a different language, or both — without running the query again. Call this, never retype a table by hand, whenever the user asks to see the SAME numbers another way ("as a table", "as a line chart", "in English", "بالعربي"). Translating a table yourself corrupts the data: vehicle, branch and driver names are stored per language and cannot be translated by guessing. If the numbers themselves should change — different metric, dimension or date range — call run_query instead.

Turn a name the user typed ("Riyadh", "Truck 204") into a real id. NEVER invent or guess ids — always resolve them here first. Returns typed candidates; if needsDisambiguation is true, ask the user which one they mean.

Execute a report. Supply a definition built from catalog metric keys and ids from resolve_entity. Never include a company id — scoping is automatic. If the call is rejected, the error lists what is valid; fix the definition and retry.

Re-run a saved report, optionally overriding its filters (new date range, branch, vehicle). Overrides are merged onto the saved definition and re-validated.

Save the definition of the report just run, so the user can re-run it later with different filters. Only call after the user confirms the result is what they wanted.

Find which metrics can answer a question. ALWAYS call this before run_query. Returns matching metric keys with descriptions, units, and an ambiguity flag — if a match reports needsDisambiguation, ask the user which definition they mean instead of guessing.