---
name: recalls-jobs
description: "Step-by-step job recipes for the Recall Check MCP server: Check vehicle recalls; Decode a VIN; Search product recalls. Use when the user asks things like \"Does my 2018 Honda Accord have any recalls?\" or \"Decode this VIN: 1HGCM82633A004352.\""
license: MIT
---

# Recall Check jobs

Each section below walks through one job with the tools of the `recalls` MCP server. The same recipes are MCP prompts (prompts/list) on `https://api.openkrill.app/gateway/mcp`.
Connect the server at `https://recalls.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Check vehicle recalls

Job: Check vehicle recalls, with the Recall Check MCP server.

Use the `check_vehicle_recalls` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Does my 2018 Honda Accord have any recalls?"

Steps:
1. Call `check_vehicle_recalls` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `year`, `make`, `model`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"year":2018,"make":"Honda","model":"Accord"}`
4. For the request "Does my 2018 Honda Accord have any recalls?", a correct answer looks like this: status ok, a vehicle of 2018 Honda Accord, a totalRecalls count and up to 10 recalls newest first, each with campaignNumber, reportedOn, component, summary, consequence and remedy, plus the US-only notice. The list includes campaign 20V314000 (fuel pump).
5. Follow the server's own rules:
   - Use these tools for recall questions about vehicles, consumer products, food, pet food and drugs sold in the United States.
   - For a vehicle, call check_vehicle_recalls with its year, make and model; when the user gives a VIN, call decode_vin first and use the year, make and model it returns.
   - Convert "this week" or "this month" into withinDays.
   - Never ask the user for their name, address or license plate: the lookups need only a year, make and model, a VIN, or a product description.
   - Always tell the user the data is US only and not a safety guarantee, and for a specific car point them to nhtsa.gov/recalls with their VIN.
   - Do not tell the user an item is safe because nothing was found.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `check_vehicle_recalls`).

## Decode a VIN

Job: Decode a VIN, with the Recall Check MCP server.

Use the `decode_vin` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Decode this VIN: 1HGCM82633A004352."

Steps:
1. Call `decode_vin` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `vin`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"vin":"1HGCM82633A004352"}`
4. For the request "Decode this VIN: 1HGCM82633A004352.", a correct answer looks like this: status ok and a vehicle of 2003 Honda Accord, trim EX-V6, Coupe body class, manufacturer American Honda Motor Co., engine 3.0L 6-cyl, fuel Gasoline, with no check-digit warning.
5. Follow the server's own rules:
   - Use these tools for recall questions about vehicles, consumer products, food, pet food and drugs sold in the United States.
   - For a vehicle, call check_vehicle_recalls with its year, make and model; when the user gives a VIN, call decode_vin first and use the year, make and model it returns.
   - Convert "this week" or "this month" into withinDays.
   - Never ask the user for their name, address or license plate: the lookups need only a year, make and model, a VIN, or a product description.
   - Always tell the user the data is US only and not a safety guarantee, and for a specific car point them to nhtsa.gov/recalls with their VIN.
   - Do not tell the user an item is safe because nothing was found.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `decode_vin`).

## Search product recalls

Job: Search product recalls, with the Recall Check MCP server.

Use the `search_product_recalls` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Is the Joolz Aer2 car seat adapter recalled?"

Steps:
1. Call `search_product_recalls` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `query`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"query":"Joolz Aer2 car seat adapter"}`
4. For the request "Is the Joolz Aer2 car seat adapter recalled?", a correct answer looks like this: status ok with at least one recall, recallNumber 26568, titled Joolz Recalls Aer2 Car Seat Adapters for Strollers, with the fall hazard, a refund remedy, the Joolz contact and the CPSC link. Because the question mentions a car seat, the message adds that car seats themselves are NHTSA recalls this plugin cannot see.
5. Follow the server's own rules:
   - Use these tools for recall questions about vehicles, consumer products, food, pet food and drugs sold in the United States.
   - For cribs, strollers, toys, appliances and other consumer goods, and for car seat accessories, call search_product_recalls with the brand and product; for a car seat or tire itself it cannot see NHTSA recalls, so say that and point to nhtsa.gov/recalls.
   - Convert "this week" or "this month" into withinDays.
   - Never ask the user for their name, address or license plate: the lookups need only a year, make and model, a VIN, or a product description.
   - Always tell the user the data is US only and not a safety guarantee, and for a specific car point them to nhtsa.gov/recalls with their VIN.
   - Do not tell the user an item is safe because nothing was found.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `search_product_recalls`).
