Skip to main content
Glama
Sign In

Dutify

by ai.dutify.mcp
OverviewDiscussionsAdmin

pm_update_notification_channel

Destructive

Turn individual Codexum (wiki) or Roadmarq (feedback) notifications on or off for one delivery channel (app, email or browser) of the current user. Pass settings as a map of setting key to true|false; only the keys you send change, the others keep their value (every key starts on). Codexum keys: pageUpdated, pageSharedWithMe, mentionedInPage, pageComments. Roadmarq keys: newFeedback, feedbackStatusChanged, feedbackVotes, feedbackComments. Returns the whole channel after the update: {settings: {key: true|false}} with every key of the module. pm_get_notification_settings shows the current values. Project Management notifications are not changed here: PM uses PUT /v1/users/settings/notifications/{channel}, which this server does not expose as a tool. API-key scope: users:write.

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": {
      "module": "<module>",
      "channel": "<channel>",
      "settings": "<settings>"
    },
    "name": "pm_update_notification_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleYescodexum (wiki) or roadmarq (feedback)
accountNoMulti-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
channelYesDelivery channel
settingsYesSetting key to true (on) or false (off). At least one key, all of the chosen module: codexum: pageUpdated, pageSharedWithMe, mentionedInPage, pageComments; roadmarq: newFeedback, feedbackStatusChanged, feedbackVotes, feedbackComments.
workspaceNoWorkspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
-  "app",
-  "browser",
-  "email"
-]New value: +[
+  "app",
+  "email",
+  "browser"
+]
    • removedInput schema / properties / enabled
      Removed value: -{
-  "description": "Turn the channel on (true) or off (false)",
-  "type": "boolean"
-}
    • changedInput schema / properties / module / description
      Previous value: -"Module identifier from the aggregated settings — e.g. 'comments', 'mentions', 'assignments', 'due_date', 'automation', 'invitation'"New value: +"codexum (wiki) or roadmarq (feedback)"
    • addedInput schema / properties / module / enum
      Added value: +[
+  "codexum",
+  "roadmarq"
+]
    • addedInput schema / properties / settings
      Added value: +{
+  "additionalProperties": false,
+  "description": "Setting key to true (on) or false (off). At least one key, all of the chosen module: codexum: pageUpdated, pageSharedWithMe, mentionedInPage, pageComments; roadmarq: newFeedback, feedbackStatusChanged, feedbackVotes, feedbackComments.",
+  "minProperties": 1,
+  "properties": {
+    "feedbackComments": {
+      "type": "boolean"
+    },
+    "feedbackStatusChanged": {
+      "type": "boolean"
+    },
+    "feedbackVotes": {
+      "type": "boolean"
+    },
+    "mentionedInPage": {
+      "type": "boolean"
+    },
+    "newFeedback": {
+      "type": "boolean"
+    },
+    "pageComments": {
+      "type": "boolean"
+    },
+    "pageSharedWithMe": {
+      "type": "boolean"
+    },
+    "pageUpdated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
    • changedInput schema / required
      Previous value: -[
-  "module",
-  "channel",
-  "enabled"
-]New value: +[
+  "module",
+  "channel",
+  "settings"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description earns credit by clarifying that this is a partial update ("only the keys you send change, the others keep their value"), that every key defaults to on, and that the full channel is returned. It also discloses the required API-key scope `users:write`, which annotations cannot convey. It doesn't discuss reversibility beyond the default-on note, so not 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.

Conciseness4/5

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

Front-loaded with the action and scope, then keys, return shape, alternative, and auth scope. The enumeration of Codexum and Roadmarq keys repeats the schema's nested property description, so a sentence could be trimmed, but nothing is confusing.

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 mutation tool with no output schema, the description supplies the return shape (`{settings: {key: true|false}}` with every key of the module), the merge semantics, the module/channel scope, the read alternative, and the required auth scope. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description adds genuinely new semantics: the default value of every key (on) and the partial-merge behavior of `settings`. The per-module key lists largely duplicate the schema's `settings` description, which caps this at 4.

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+resource+scope: turning individual Codexum/Roadmarq notifications on or off for one delivery channel of the current user. It explicitly separates itself from pm_get_notification_settings and from Project Management notifications, so an agent can route correctly without opening the schema.

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?

Gives a clear read-side alternative ("pm_get_notification_settings shows the current values") and an explicit exclusion (PM notifications are not changed here because the endpoint isn't exposed). What's missing is a stated precondition or when-not for the write path itself (e.g. do not call with an empty map), but the routing context is solid.

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

All Dutify toolsInspect
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