Skip to main content
Glama
Sign In

HelpWell

by ai.helpwell.app
OverviewDiscussionsAdmin

Update team notification defaults

update_team_notification_defaults
Destructive

Change the notification defaults everyone on the team starts with (people who customised their own keep theirs). Anything left out stays.

Input Schema

NameRequiredDescriptionDefault
kindsNoPer notification kind, which channels deliver it (inApp, push, email, slack). Only the kinds and channels given change.
quietNoWorking hours: notifications outside them wait. days are 0 (Sunday) to 6; times like 09:00.
digestNoThe desk digest email: on or off, the hour (0 to 23) and the days (0 to 6).
timeZoneNoIANA time zone, like America/Phoenix.
waitingMinutesNoMinutes a customer waits before "waiting long" fires.
emailDelayMinutesNoMinutes before an unread notification is emailed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / kinds / properties / issue_assigned
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "email": {
+      "type": "boolean"
+    },
+    "inApp": {
+      "type": "boolean"
+    },
+    "push": {
+      "type": "boolean"
+    },
+    "slack": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / kinds / properties / issue_fixed
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "email": {
+      "type": "boolean"
+    },
+    "inApp": {
+      "type": "boolean"
+    },
+    "push": {
+      "type": "boolean"
+    },
+    "slack": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / kinds / properties / issue_new
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "email": {
+      "type": "boolean"
+    },
+    "inApp": {
+      "type": "boolean"
+    },
+    "push": {
+      "type": "boolean"
+    },
+    "slack": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / kinds / properties / ai_spend
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "email": {
+      "type": "boolean"
+    },
+    "inApp": {
+      "type": "boolean"
+    },
+    "push": {
+      "type": "boolean"
+    },
+    "slack": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavior: the blast radius (all team members on defaults, customized users exempt) and patch semantics ('Anything left out stays'), though it omits whether an admin role is required and whether the change can be reverted.

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?

A single sentence with the affected population front-loaded and the two qualifying clauses in parentheses; every clause carries information an agent needs.

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

Completeness4/5

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

For a six-parameter, all-optional nested patch tool with full schema documentation and no output schema, the description covers the two things the schema cannot: who the change affects and that omitted fields persist. It stops short of stating permission requirements or reversibility, which matters for a destructive team-wide mutation.

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 description coverage is 100% and the schema already spells out each parameter, including 'Only the kinds and channels given change.' The description's 'Anything left out stays' reinforces the partial-update contract at the top level but adds no format detail beyond the schema, so 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 and resource ('Change the notification defaults') plus the exact scope ('everyone on the team starts with'), which cleanly separates it from the personal-preference siblings update_my_notification_preferences and reset_my_notification_preferences without needing to name them.

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

Usage Guidelines3/5

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

The parenthetical '(people who customised their own keep theirs)' tells the agent what this tool will not touch, which implies when it is appropriate, but no alternative tool is named and no prerequisite (e.g. admin role) or when-not condition is stated explicitly.

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

All HelpWell 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