To let an assistant use these tools, grant Organisation on the consent screen, or just
My notifications under its Fine-tune. The scope is notifications.
Read tools work with Read only or Read & write access; write tools only with
Read & write.
Your assistant doesn't see these tools straight away. It finds them with search_tools or
describe_tools, and runs one with use_tool, passing its name and
arguments. Most assistants do this for you: just ask for what you want.
What your assistant is told about this group
Your own notifications (read them, mark them read) and which channels each kind of alert reaches you on. Personal: it needs a signed-in person, and only changes their own settings, never a colleague's.
The descriptions below are the ones your assistant reads, so they're written for it. When a connection covers more than one
organisation, the assistant passes org (the organisation's slug, from list_orgs) to say which one.
list_my_notifications
Read List my notifications
Your own notifications (escalations, approvals, alerts) plus org and platform announcements, newest first, 20 per page. category is ai or human.
Arguments
| Field | Type | Description |
|---|---|---|
| unread_only | boolean | |
| category | string |
One of: "ai", "human"
|
| page | integer | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
mark_notification_read
Write Mark a notification read
Marks one of your notifications read.
Arguments
| Field | Type | Description |
|---|---|---|
| id required | string | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
mark_all_notifications_read
Write Mark all notifications read
Marks every notification you can see as read.
Arguments
| Field | Type | Description |
|---|---|---|
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
get_my_notification_preferences
Read Get my notification settings
Which channels each kind of alert reaches you on (your choice, else the default), and the contact methods and iOS app sign-ins you've added (push needs the iOS app). Security and billing account alerts always send.
Arguments
| Field | Type | Description |
|---|---|---|
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
update_my_notification_preferences
Write Change my notification settings
Sets which channels alerts reach you on: preferences maps an alert's event_key (from get_my_notification_preferences) to { channel => true/false }. Channels you leave out of an alert turn OFF for it, so send every channel you want on. Alerts not named are unchanged.
Arguments
| Field | Type | Description |
|---|---|---|
| preferences required | object | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |
reset_my_notification_preference
Write Reset a fine-tuned alert setting
Puts a fine-tuned alert setting (a scoped event_key like "lifecycle_operational/<product>/<event>" or "milestone_reached/<milestone>") back to inheriting from the level above.
Arguments
| Field | Type | Description |
|---|---|---|
| event_key required | string | |
| org | string | Organisation slug: required when this authorization covers more than one organisation (see list_orgs) |