append_project_annotation
Append one annotation to project context. Append-only: goals, activation events, glossary entries, and existing annotations stay in place. Allowed fields are project, occurred_at (ISO-8601 timestamp, stored as UTC), title (max 120 characters), and an optional note (max 500 characters). The annotation identity is normalized occurred_at plus title. A duplicate returns 200 with appended false and keeps the stored note. The 100 annotation cap returns 409 and stores nothing. Use this for a meaningful landing page, pricing, onboarding, feature, release, or experiment change. Do not store git commit logs, noisy edits, PII, secrets, or long notes.
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": {
"project": "<project>",
"occurred_at": "<occurred_at>",
"title": "<title>"
},
"name": "append_project_annotation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Optional short note, max 500 characters | |
| title | Yes | Short annotation title, max 120 characters | |
| project | Yes | Project name or ID | |
| occurred_at | Yes | ISO-8601 timestamp when the major product change happened |