Damoov Telematics

View saved version →

---
name: damoov-mcp-breakdown
description: Breaks down Damoov fleet and driving metrics by an approved dimension or ranks top contributors. Use when a user asks for daily detail, trip-type composition, event categories, drivers, trips, segments, or top contributors.
---

# Damoov metric breakdown

Use the Damoov Telematics MCP tools.

## Workflow

1. Resolve the company with `list_companies`.
2. Call `list_metrics` to confirm the metric supports the requested dimension.
3. For grouped analysis, call `breakdown_by` with a limit no greater than 50.
4. For ranked driver or trip entities, call `get_top_contributors` with a limit no greater than 50.
5. Report the dimension, period, filters, returned rows, and whether the result was truncated.

## Rules

- Use only dimensions and entity types advertised by `list_metrics`.
- If `truncated=true`, state that additional rows exist; do not present the output as complete.
- For a daily breakdown, preserve ascending date order.
- Do not combine pages or periods in ways that change the requested metric semantics.
- Never expose raw SQL, database schema, credentials, tokens, or internal identifiers beyond tool output.
- Avoid `active_drivers`; it has a known timeout limitation.

View saved version →

---
name: damoov-mcp-compare-periods
description: Compares Damoov fleet or driving metrics between two periods and explains the change. Use when a user asks for period-over-period change, trends, increases, decreases, or reasons for a metric difference.
---

# Damoov period comparison

Use the Damoov Telematics MCP tools.

## Workflow

1. Resolve the company with `list_companies`.
2. Use `list_metrics` if the metric ID or supported periods are unclear.
3. Confirm two non-overlapping periods when the user's wording is ambiguous.
4. Call `compare_periods`.
5. When the metric supports it and the user asks why it changed, call `explain_change`.
6. Report:
   - base-period value;
   - comparison-period value;
   - absolute delta;
   - percentage change when available;
   - exact period boundaries;
   - non-causal change components when returned.

## Rules

- Treat delta as comparison value minus base value.
- Describe `explain_change` output as non-causal components, not proven causes.
- Never invent missing data or infer unsupported causality.
- Keep the company and filters identical across both periods unless the user explicitly requests otherwise.
- Do not expose raw SQL, credentials, tokens, or database schema.
- Avoid `active_drivers`; it has a known timeout limitation.

View saved version →

---
name: damoov-mcp-metric-qa
description: Retrieves Damoov fleet and driving metric values for a company and time period. Use when a user asks for trip count, distance, safety score, harsh events, or another single Damoov metric.
---

# Damoov metric lookup

Use the Damoov Telematics MCP tools.

## Workflow

1. Call `list_companies`.
2. If several companies are available and the user did not identify one, ask which company to use.
3. Call `list_metrics` when the requested metric ID or supported period is unclear.
4. Call `get_metric` with the selected company, metric, period, and only the filters requested by the user.
5. Report the value, unit, exact interpreted period, and data freshness when returned.

## Rules

- Never invent a company, metric ID, period, filter, or result.
- If no company is available, explain that the user lacks company access.
- Do not expose raw SQL, database schema, credentials, tokens, or internal policy details.
- Do not call `no_op` for an analytics request.
- Avoid `active_drivers`; it has a known timeout limitation.