Update to Damoov Telematics

{
  "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.",
  "included_files": [],
  "name": "damoov-mcp-breakdown",
  "skill_md_contents": "---\nname: damoov-mcp-breakdown\ndescription: 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.\n---\n\n# Damoov metric breakdown\n\nUse the Damoov Telematics MCP tools.\n\n## Workflow\n\n1. Resolve the company with `list_companies`.\n2. Call `list_metrics` to confirm the metric supports the requested dimension.\n3. For grouped analysis, call `breakdown_by` with a limit no greater than 50.\n4. For ranked driver or trip entities, call `get_top_contributors` with a limit no greater than 50.\n5. Report the dimension, period, filters, returned rows, and whether the result was truncated.\n\n## Rules\n\n- Use only dimensions and entity types advertised by `list_metrics`.\n- If `truncated=true`, state that additional rows exist; do not present the output as complete.\n- For a daily breakdown, preserve ascending date order.\n- Do not combine pages or periods in ways that change the requested metric semantics.\n- Never expose raw SQL, database schema, credentials, tokens, or internal identifiers beyond tool output.\n- Avoid `active_drivers`; it has a known timeout limitation.\n"
}