Save research into DevVault
devvault_save_researchSave current research into structured vault containers, grouped by topic and nested sub-topics, so future sessions can retrieve findings without re-deriving. Reuse external keys to update in place.
Instructions
File the current conversation's findings into the user's vault as structured containers, so neither of you has to re-derive them next time. You decide the structure: group by topic, one topic per container, and nest sub-topics as children. Write real titles. Constraints are enforced server-side and anything over them is repaired automatically (long paragraphs split, extra blocks spill into continuation containers, deep nesting is flattened and linked) — the response tells you exactly what was adjusted, so report that to the user. Always set external_key on every container: re-running the same research then updates in place instead of duplicating. Supplying agent_rules alongside the research is worth doing — it saves a future session from re-reading the prose.
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": {
"containers": "<containers>"
},
"name": "devvault_save_research"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | 'update' reuses containers matching on external_key. | update |
| parent_id | No | Nest the import under an existing container. | |
| containers | Yes | Flat list. The first entry is the root (parent: null); every other entry points at an earlier index. | |
| collection_name | No | Names the collection this import creates. Defaults to the root title. | |
| collection_description | No | One or two sentences on what this collection covers and when it applies. This is what future task descriptions are matched against, so make it specific. |