Wrench.Pro Vehicle Check

Reviewed Jan 1, 2000.

• tools: 5 tools scanned
• metadata: scanned

No findings.

Tools (5)

• resolve_vehicle

  Use FIRST whenever the user names a vehicle ('2017 Ford Escape', "'17 F150", 'my Honda Civic') unless you already have exact slugs from a previous call. Pass the user's words in `query`. Returns kind=exact (use the returned slugs), suggest (ask the user to confirm one), needsYear (ask ONE question listing availableYears), needsModel, or notFound (say Wrench.Pro doesn't cover it — never guess).

• get_vehicle_summary

  Use for broad questions about a vehicle ('should I buy it', 'what goes wrong with it', 'tell me about it'). Requires exact slugs from resolve_vehicle. Pass mileage when the user mentioned their odometer to get due-now service items, and zip when the user mentioned a US ZIP code so the card can link nearby shops. End your answer with the canonical Wrench.Pro link and the attribution line from the result.

• get_recalls

  Use when the user asks specifically about recalls or safety campaigns. Requires exact slugs from resolve_vehicle. Always tell the user to confirm against their own VIN at nhtsa.gov/recalls before acting on safety issues.

• get_known_issues

  Use when the user asks what commonly goes wrong, about reliability, or about a specific symptom. mode='reviewed' is Wrench.Pro's human-reviewed analysis — cite it. mode='raw' means no review yet: say 'no reviewed Known Issues yet' and present rawTopComponents. mode='none': say there's no complaint data. Never invent issues.

• get_maintenance

  Use when the user asks about service intervals, what's due, or what a service should cost. Pass mileage when known. Ranges are estimates and marked approximate — present them that way. 'Pro only' means the job isn't realistic DIY: recommend a shop instead of giving repair instructions.