How to Check a Used Car Before Buying with Copilot
Check a Used Car Before Buying with Copilot and ToolRouter. Pull structured vehicle history data for integration into automotive apps and tools.
Tool
Use Copilot with Vehicle Data to pull structured vehicle history data for an automotive application, fleet management tool, or dealer management system. Copilot is best when the history data needs to be typed, schema-matched, and integrated into an existing codebase.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
Steps
Once connected (see setup above), use the Vehicle Data tool:
- Identify the registration plate and define your application schema for vehicle history data.
- Ask Copilot to run `dvsa_mot`, `plate_lookup`, `inspection_history`, and `check_recalls` via `vehicle-data`.
- Have Copilot return the combined result as typed JSON matching your schema.
- Integrate the output into your vehicle listing, fleet record, or inspection system.
Example Prompt
Try this with Copilot using the Vehicle Data tool
Use vehicle-data to check registration plate AB12 CDE. Run dvsa_mot, plate_lookup, inspection_history, and check_recalls. Return JSON: {registration: string, make: string, model: string, mot_history: Array<{date, result, mileage, advisories}>, outstanding_recalls: number, history_verdict: string}.
Tips
- Include `history_verdict` as a computed string (clean/advisory/concern) so your UI can display a clear status badge.
- Return `outstanding_recalls` as a number so your app can flag vehicles with open recalls with a single comparison.
- Keep `mot_history` as a sorted array (newest first) for consistent display.