describe_item
Writes a searchable name and note for one archive item, turning what is visible in the image into plain Markdown saved beside the file.
Instructions
Write the name and note for one item in the archive.
This is the tool that earns the server its keep. Describing an archive by hand is the slow, valuable work that makes everything else findable — search by meaning has nothing to rank without it, and list_folders will tell you exactly which folders are thin.
Look at the image with view_inspo FIRST, then describe what is actually there. A guess from the filename is worse than no description: it will be searched, believed, and never checked.
The NAME is one line — what this is, in the words somebody would look for. It becomes the item's name everywhere in the app. The NOTE is the longer thought: why it was kept, what to steal from it. Either can be left out to keep what is already written; passing an empty string clears it.
Writes to the _manifest.md file beside the image, in plain Markdown, so the words outlive this app.
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": {
"path": "<path>"
},
"name": "describe_item"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | One line. What this is. Omit to leave the existing one. | |
| note | No | The longer thought. Omit to leave the existing one. | |
| path | Yes | The item, as search_inspo reports it: "@<root>/<folder>/<file>". |