Synoptic

Toggle notification channel

set_notification_channel

DestructiveIdempotent

Turn the in-app or email channel on or off for the whole signed-in account, not per device. While a channel is off, none of the account’s notifications are delivered on it. Per-event choices made with update_notification_preferences are kept and apply again once it is back on. Returns the saved settings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`enabled`	Yes	true turns the channel on; false stops all delivery on it
`notificationType`	Yes	IN_APP or EMAIL; PUSH has no account-wide switch

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notifications`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 18, 2026
- addedInput schema / properties / enabled / description
```
Added value: +"true turns the channel on; false stops all delivery on it"
```
- addedInput schema / properties / notificationType / description
```
Added value: +"IN_APP or EMAIL; PUSH has no account-wide switch"
```
- 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.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: the effect while off ('none of the account's notifications are delivered'), the account-wide scope, and that the change is reversible with preferences preserved. It does not explicitly flag the destructive/reversible tradeoff in the annotation's terms, keeping it below a 5.

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 tight sentences, scoping constraint front-loaded, and the interaction with the sibling tool placed after the core behavior. No filler; every sentence carries information.

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 2-param idempotent toggle with an output schema and full annotation coverage, the description supplies everything an agent needs: scope, on/off effect, reversibility, and sibling interaction.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented, including the IN_APP/EMAIL enum and the PUSH exclusion. The description reinforces the channel scope but adds little parameter-level syntax beyond the schema, so the baseline 3 applies.

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 specific verb (turn on/off) and resource (in-app or email notification channel) with explicit scope ('whole signed-in account, not per device'). This cleanly separates it from the sibling update_notification_preferences, which handles per-event choices.

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

Usage Guidelines4/5

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

It names the alternative (update_notification_preferences), clarifies the division of labor (account-wide channel vs. per-event), and explains that per-event choices survive a toggle. It stops short of an explicit 'use this when / use that when' routing statement, so a 4 rather than a 5.

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?