Find parts for a job
find_partsFree. Ranks the library’s parts for a job described in words, with why each fits and what it costs on the target platform (median ms a frame at 1920×1080 on a measured machine and tier). Strong matches for the job come first (each part says match: strong or loose), then looser ones; within each, parts that fit the platform and budget lead, then those over the budget (overBudget), then those that need WebGPU on a platform without it (blocked). For an interface job, 3D, simulation and effects parts rank lower. Each part says what it runs in (runsIn): raw WebGPU passes, a three.js scene, a 2D canvas or the DOM; a three.js part needs a three.js app, so check it against your renderer before installing. When the words name a look or ask for one, the matching looks come back too. Search by the job, not by a name.
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": {
"job": "<job>"
},
"name": "find_parts"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | Yes | What the part has to do, e.g. "date range filter for a dashboard" or "grass that bends round a walker". | |
| kit | No | Optional: a kit id (e.g. dashboard) to search only its parts and those of the kits it is built on. | |
| limit | No | At most this many parts (default 10). | |
| budget | No | Ms a frame the part may cost on that platform (the worse of GPU and CPU). | |
| platform | No | The target: desktop (the reference laptop, the default), laptop (integrated GPU), phone, a machine id from a part’s costs, or "no-webgpu" for browsers without it. |