Add Note Tool
add_noteSave project context colleagues need—access steps, conventions, gotchas, or locations—and notify them with @Name. Mark outdated notes obsolete or replace them with corrected text.
Instructions
Saves something colleagues should know about a project (@Name in it notifies that colleague): how to get access, a convention, a gotcha, where something lives. Never secrets, passwords or tokens. A note that is no longer true is marked outdated with obsolete (its id comes with project_brief), alone or with the text of the note that replaces it. Only when the person asks or agrees.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "add_note"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | No | The git remotes of the working directory (git remote -v). | |
| text | No | One or two sentences a colleague can act on, e.g. "Staging is reachable only through the office VPN." Markdown works: `code`, links, a short list. | |
| project | No | Project slug or name, when there is no repo (or from a .cemainou file). | |
| session | No | This session's id, from the cemainou line at the start of the session. The session's project wins over the repo. | |
| obsolete | No | The id of a note that is no longer true (from project_brief): it is marked outdated. With text, the new note replaces it. |