Synoptic

Update notification preferences

update_notification_preferences

DestructiveIdempotent

Replace notification channel preferences for mentions, new followers, subscribed-author posts, and system events. Read current settings first; provide all four event groups. Empty arrays disable an event group. IN_APP and EMAIL also need their account-wide switch on; see set_notification_channel. PUSH has no switch.

Input Schema

TableJSON Schema

Name	Required	Description
`system`	Yes	Channels (PUSH, EMAIL, IN_APP) for system notices, such as subscription, export and access updates; [] turns it off
`mentions`	Yes	Channels (PUSH, EMAIL, IN_APP) for mentions in posts; [] turns it off
`newFollowers`	Yes	Channels (PUSH, EMAIL, IN_APP) for new followers; [] turns it off
`subscribedAuthorPost`	Yes	Channels (PUSH, EMAIL, IN_APP) for new discussion posts in streams the user owns; [] turns it off

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notifications`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 18, 2026
- addedInput schema / properties / mentions / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for mentions in posts; [] turns it off"
```
- removedInput schema / properties / newFollowers / $ref
```
Removed value: -"#/properties/mentions"
```
- addedInput schema / properties / newFollowers / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for new followers; [] turns it off"
```
- addedInput schema / properties / newFollowers / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / newFollowers / maxItems
```
Added value: +3
```
- addedInput schema / properties / newFollowers / type
```
Added value: +"array"
```
- removedInput schema / properties / subscribedAuthorPost / $ref
```
Removed value: -"#/properties/mentions"
```
- addedInput schema / properties / subscribedAuthorPost / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for new discussion posts in streams the user owns; [] turns it off"
```
- addedInput schema / properties / subscribedAuthorPost / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / subscribedAuthorPost / maxItems
```
Added value: +3
```
- addedInput schema / properties / subscribedAuthorPost / type
```
Added value: +"array"
```
- removedInput schema / properties / system / $ref
```
Removed value: -"#/properties/mentions"
```
- addedInput schema / properties / system / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for system notices, such as subscription, export and access updates; [] turns it off"
```
- addedInput schema / properties / system / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedInput schema / properties / system / maxItems
```
Added value: +3
```
- addedInput schema / properties / system / type
```
Added value: +"array"
```
- addedOutput schema / properties / notifications / properties / EMAIL / description
```
Added value: +"Account-wide email switch; while false, no event group is delivered by email"
```
- addedOutput schema / properties / notifications / properties / IN_APP / description
```
Added value: +"Account-wide in-app switch; while false, no event group is delivered in-app"
```
- addedOutput schema / properties / notifications / properties / mentions / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for mentions in posts; [] turns it off"
```
- removedOutput schema / properties / notifications / properties / newFollowers / $ref
```
Removed value: -"#/properties/notifications/properties/mentions"
```
- addedOutput schema / properties / notifications / properties / newFollowers / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for new followers; [] turns it off"
```
- addedOutput schema / properties / notifications / properties / newFollowers / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / notifications / properties / newFollowers / maxItems
```
Added value: +3
```
- addedOutput schema / properties / notifications / properties / newFollowers / type
```
Added value: +"array"
```
- removedOutput schema / properties / notifications / properties / subscribedAuthorPost / $ref
```
Removed value: -"#/properties/notifications/properties/mentions"
```
- addedOutput schema / properties / notifications / properties / subscribedAuthorPost / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for new discussion posts in streams the user owns; [] turns it off"
```
- addedOutput schema / properties / notifications / properties / subscribedAuthorPost / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / notifications / properties / subscribedAuthorPost / maxItems
```
Added value: +3
```
- addedOutput schema / properties / notifications / properties / subscribedAuthorPost / type
```
Added value: +"array"
```
- removedOutput schema / properties / notifications / properties / system / $ref
```
Removed value: -"#/properties/notifications/properties/mentions"
```
- addedOutput schema / properties / notifications / properties / system / description
```
Added value: +"Channels (PUSH, EMAIL, IN_APP) for system notices, such as subscription, export and access updates; [] turns it off"
```
- addedOutput schema / properties / notifications / properties / system / items
```
Added value: +{
+  "enum": [
+    "PUSH",
+    "EMAIL",
+    "IN_APP"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / notifications / properties / system / maxItems
```
Added value: +3
```
- addedOutput schema / properties / notifications / properties / system / type
```
Added value: +"array"
```
First observedOct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations say destructiveHint=true and idempotentHint=true, but the description goes further by explaining WHAT gets destroyed: this is a full replacement, all four event groups must be supplied, and any group omitted or sent as [] is turned off. It also discloses the hidden dependency that IN_APP/EMAIL require an account-wide switch while PUSH does not — a behavioral rule absent from the annotations and schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, each carrying distinct information: scope, pre-read/full-replacement rule, disable semantics, and the switch dependency. Front-loaded with the verb and resource, with no filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, full-replacement mutation with four required parameters, the description covers scope, overwrite semantics, the pre-read step, disable behavior, and the cross-tool switch dependency. An output schema exists, so return values need no explanation, leaving no significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-parameter descriptions already document the enum values and the '[] turns it off' semantics, setting the baseline at 3. The description adds meaning beyond that by tying the arrays to the account-wide switch requirement and the PUSH exception, which the schema does not mention.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb (Replace) and resource (notification channel preferences) and enumerates the exact scope: mentions, new followers, subscribed-author posts, system events. The word 'Replace' plus the reference to set_notification_channel clearly separates it from the sibling that toggles account-wide channel switches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete prerequisites ('Read current settings first; provide all four event groups') and routes the agent to the sibling for the master switch ('IN_APP and EMAIL also need their account-wide switch on; see set_notification_channel'). It also explains the disable condition (empty arrays) and carves out PUSH as needing no switch, which is exactly the kind of when/when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Synoptic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?