Mark a developer notification as read
amber_mark_notification_readMarks a developer notification as read and permanently removes it from the developer_notifications block after the user has acknowledged its content.
Instructions
Dismiss a developer notification after the user has acknowledged it. Permanently removes it from the developer_notifications block. That block is appended to a tool response ONLY WHEN there is at least one unread notification -- most responses will not contain it, and its absence means there is nothing pending, not that the feature is missing.
Side effects: deletes the notification row from the user's database. Idempotent in intent but returns code: not_found if already dismissed. Only call after the user has seen the notification content. Not rate-limited.
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": {
"notification_id": "<notification_id>"
},
"name": "amber_mark_notification_read"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notification_id | Yes | Positive integer from the `id` field of a notification in `developer_notifications`. Example: if the block contains `{id: 42, message: "..."}`, pass 42. Each ID is unique and single-use. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | Always `read`: the notification is acknowledged and will not be attached to further responses. | |
| notification_id | Yes | The notification that was acknowledged. |