---
name: certpacket-jobs
description: "Step-by-step job recipes for the CertPacket MCP server: Find the safety rules and certificate; Find CPSC-accepted labs; Check a lab report. Use when the user asks things like \"Which safety rules and certificate does a painted wooden toy for 3 year olds need?\" or \"Find CPSC-accepted labs in Vietnam that can test lead in paint and lead content.\""
license: MIT
---

# CertPacket jobs

Each section below walks through one job with the tools of the `certpacket` MCP server. The same recipes are MCP prompts (prompts/list) on `https://certpacket.openkrill.app/mcp`.
Connect the server at `https://certpacket.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.

## Find the safety rules and certificate

Job: Find the safety rules and certificate, with the CertPacket MCP server.

Use the `find_cert_rules` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Which safety rules and certificate does a painted wooden toy for 3 year olds need?"

Steps:
1. Call `find_cert_rules` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `product`.
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: `{"product":"mini crib"}`
4. For the request "Which safety rules and certificate does a painted wooden toy for 3 year olds need?", a correct answer looks like this: Category toys, certificate CPC, rules including ASTM F963, lead in paint and lead content with their citations and lab flags.
5. Follow the server's own rules:
   - Always call find_cert_rules first for any product the user asks about (even commercial or industrial equipment), so the tool checks coverage or returns status not_covered with the official CPSC guidance link; if the user sent a photo, describe the product, its age and features in words.
   - Report the numeric score and readiness, list blockers first, then fixes, then checks, and say each fix in plain words.
   - If status is not_covered, say the product type is outside the seeded list and give the guidanceUrl link without inventing other agency rules.
   - Never say a product is compliant or a certificate is correct.
   - End every answer with the notice field text.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `find_cert_rules`).

## Find CPSC-accepted labs

Job: Find CPSC-accepted labs, with the CertPacket MCP server.

Use the `find_accepted_labs` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Find CPSC-accepted labs in Vietnam that can test lead in paint and lead content."

Steps:
1. Call `find_accepted_labs` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `ruleIds`.
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: `{"ruleIds":["lead-paint"],"country":"Viet Nam","limit":5}`
4. For the request "Find CPSC-accepted labs in Vietnam that can test lead in paint and lead content.", a correct answer looks like this: Labs in Vietnam accepted for both methods, each with location, accreditation body and CPSC detail link.
5. Follow the server's own rules:
   - Pass its testedRuleIds to find_accepted_labs, with f963Sections and metalParts when they apply.
   - Report the numeric score and readiness, list blockers first, then fixes, then checks, and say each fix in plain words.
   - If status is not_covered, say the product type is outside the seeded list and give the guidanceUrl link without inventing other agency rules.
   - Never say a product is compliant or a certificate is correct.
   - End every answer with the notice field text.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `find_accepted_labs`).

## Check a lab report

Job: Check a lab report, with the CertPacket MCP server.

Use the `check_lab_report` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Check this lab report for a baby bib before I file."

Steps:
1. Call `check_lab_report` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
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. For the request "Check this lab report for a baby bib before I file.", a correct answer looks like this: A readiness score, gaps by severity, and eFiling field drafts with where each value comes from.
4. Follow the server's own rules:
   - For check_lab_report, pass the uploaded PDF or public https URL as file, or the pasted text as text, plus product or ruleIds.
   - Report the numeric score and readiness, list blockers first, then fixes, then checks, and say each fix in plain words.
   - If status is not_covered, say the product type is outside the seeded list and give the guidanceUrl link without inventing other agency rules.
   - Never say a product is compliant or a certificate is correct.
   - End every answer with the notice field text.
5. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `check_lab_report`).