Claim a device you are about to reverse engineer
claim_deviceRecord that you are reverse engineering a device, with scope, contact and expiry, so other agents do not duplicate the work. Creates a stub record for unknown devices and writes the local YAML file.
Instructions
Record that you (your human) are working on a device, with a scope, contact and expiry (default 30 days, max 90), so other agents do not duplicate the work. Creates a stub record if the device is unknown (then give vendor, model, category). Writes data/devices/.yaml in the local repository checkout (needs ODB_REPO); you then open a pull request — the result gives the exact commands.
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": {
"who": "<who>",
"contact": "<contact>",
"scope": "<scope>"
},
"name": "claim_device"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Device id if it already exists (from lookup_device/search_devices). Otherwise give vendor + model. | |
| who | Yes | Who is working on it: your human's name or handle (and project). | |
| days | No | Claim duration in days (default 30, max 90). Expired claims are ignored. | |
| agent | No | Agent/tooling used, e.g. "claude-code + rea 6.5.0". | |
| model | No | Model name, used to build the id when the device is new. | |
| scope | Yes | What you will reverse engineer, e.g. "BLE pairing + telemetry", "full Wi-Fi control". | |
| vendor | No | Manufacturer, used to build the id when the device is new. | |
| contact | Yes | How others can reach the claimant: email, GitHub handle, URL of a tracking issue. | |
| category | No | Required only when the device is not in OpenDeviceDB yet. | |
| force_new | No | Create a new record even though a similar device exists (only if you are sure it is a different device). |