MoveDefense

Use this when the user asks whether MoveDefense records are complete enough for bookkeeping or review, or wants open stops, mileage anomalies, missing fuel fields, missing receipts, incomplete days, or timestamp conflicts identified. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

audit_record_quality

Use this when the user asks how much fuel a route or a merchant's delivery work likely consumed and can explicitly supply the vehicle MPG. Return an estimate with its mileage, MPG, price basis, and confidence; never present it as a logged fuel purchase. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

estimate_route_fuel_use

Use this when the user selects one result returned by search and needs its complete readable record and metadata. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

fetch

Use this when the user asks what happened on one recorded day, including the ordered stops, arrival and departure times, waits, mileage legs, load actions, and evidence counts. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

get_route_timeline

Use this when the user asks which dates contain MoveDefense records or whether records exist for a period before requesting detailed analysis. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

list_recorded_days

Use this when the user asks to see or inspect actual stored photos. First obtain record_id from search, fetch, or get_route_timeline. Accepts existing stop, fuel, inspection, or evidence IDs; optional attachment_id narrows within that record. Returns actual MCP image content with correct MIME type, hashes and provenance. Display images are derived copies; the originals stay unchanged in MoveDefense. Call show_record_evidence to render an interactive card. Use next_offset for more photos; never describe an unavailable image or infer damage causation from its location. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

get_record_photos

Use this when the user wants to find MoveDefense days, stops, fuel records, inspections, notes, photos, or receipts by natural-language keywords. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

search

Use this when the user wants photos, damage notes, evidence, where a condition was documented, or the source record, after search, fetch, get_record_photos, or get_route_timeline. Renders compact interactive evidence cards from the existing record IDs, with photos, previous/next stops and Open in MoveDefense links. It reads the authoritative records again; never accepts invented evidence. For numeric totals use existing data tools without this renderer. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

show_record_evidence

Use this when the user wants to inspect a saved route, stops, photos or chronology, after get_route_timeline. Renders the actual driver's saved day, pickups, drop-offs, inspections, notes, evidence counts and source links. Optional focus_record_id opens the relevant evidence with the immediately preceding/following stop. A documented condition and a previous handoff do not establish where damage originated. Use next_offset for additional timeline events. Numeric questions alone do not need this renderer. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

show_route_timeline

Use this when the user asks for totals or a daily or weekly breakdown of miles, stops, pickups, deliveries, recorded activity span, or wait time over a date range. The activity span is not a clock-in timesheet. Only reads the driver linked to this selected connection. Do not use this tool when the user only asks to create, change, or delete records; import Spark payouts or tips; reconcile bank deposits; or read another driver's account. Do not substitute another MoveDefense connection or its record IDs.

summarize_activity