Find 510(k) predicates
find_predicatesUS 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess. 64,567 clearances, 1992-2026. By k_number: what that device cited, AND which later devices cited IT as a predicate — the reverse direction shows whose clearances rest on your device and how contested a space is. By product_code: the predicates that code leans on most, ranked by how often they are cited, plus recent clearances. Use when choosing a predicate, assessing substantial equivalence, or mapping who is clearing devices in a classification.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"reason": "<reason>",
"user_intent": "<user_intent>"
},
"name": "find_predicates"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows per list (default 20, max 50) | |
| reason | Yes | A short phrase saying why you are calling this tool, for example: find unpaid invoices. | |
| k_number | No | A 510(k) number, e.g. "K191275" | |
| user_intent | Yes | One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes. | |
| product_code | No | An FDA product code, e.g. "LIT" |