Skip to main content
Glama

Update Alert Settings

update_alert_settings
DestructiveIdempotent

Turn mention email alerts on or off and set digest frequency in minutes. Send it to apply both settings at once and get the values now in effect back.

Instructions

Turn mention email alerts on or off and set how often the digest is sent. enabled is required on every call. A cadenceMinutes faster than the plan floor is silently raised to the floor. Both settings are replaced on every call: omitting cadenceMinutes resets it to the fastest cadence the plan allows, so pass the current value when only toggling enabled. Use get_alert_settings for availableCadences before calling. Returns the settings now in effect: enabled, cadenceMinutes after any raise to the plan floor, minIntervalMinutes (the fastest cadence the plan allows) and availableCadences, so no follow-up read is needed.

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": {
      "enabled": "<enabled>"
    },
    "name": "update_alert_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue sends mention digest emails, false stops them
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another
cadenceMinutesNoHow often digest emails go out, in minutes, e.g. 60 for hourly or 1440 for daily. Use a value from availableCadences in get_alert_settings; anything faster than the plan allows is raised to the plan's fastest. Omit to reset to the plan's fastest cadence

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.6.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / cadenceMinutes / description
      Previous value: -"Digest interval in minutes: 15, 30, 60, 120, 180, 240, 720, or 1440; raised to the plan floor when faster than allowed, reset to the fastest allowed when omitted"New value: +"How often digest emails go out, in minutes, e.g. 60 for hourly or 1440 for daily. Use a value from availableCadences in get_alert_settings; anything faster than the plan allows is raised to the plan's fastest. Omit to reset to the plan's fastest cadence"
    • addedInput schema / properties / cadenceMinutes / enum
      Added value: +[
      +  15,
      +  30,
      +  60,
      +  120,
      +  180,
      +  240,
      +  720,
      +  1440
      +]
    • changedInput schema / properties / cadenceMinutes / type
      Previous value: -"integer"New value: +"number"
    • changedInput schema / properties / enabled / description
      Previous value: -"Turn email alerts on or off"New value: +"true sends mention digest emails, false stops them"
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"The resolved settings after clamping: { enabled, cadenceMinutes, minIntervalMinutes, availableCadences }."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "availableCadences": {
      +    "description": "Cadences, in minutes, that update_alert_settings accepts on this plan",
      +    "items": {
      +      "type": "integer"
      +    },
      +    "type": "array"
      +  },
      +  "cadenceMinutes": {
      +    "description": "Digest interval in effect, in minutes",
      +    "type": "integer"
      +  },
      +  "enabled": {
      +    "description": "Whether mention digest emails are sent",
      +    "type": "boolean"
      +  },
      +  "minIntervalMinutes": {
      +    "description": "Fastest cadence the plan allows, in minutes",
      +    "type": "integer"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "enabled",
      +  "cadenceMinutes",
      +  "minIntervalMinutes",
      +  "availableCadences"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / cadenceMinutes / description
      Previous value: -"Alert frequency in minutes: 60 (hourly), 240 (4h), 720 (12h), 1440 (daily)"New value: +"Digest interval in minutes: 15, 30, 60, 120, 180, 240, 720, or 1440; raised to the plan floor when faster than allowed, reset to the fastest allowed when omitted"
    • changedOutput schema / properties / result / description
      Previous value: -"The saved alert settings with the enabled flag and effective cadence."New value: +"The resolved settings after clamping: { enabled, cadenceMinutes, minIntervalMinutes, availableCadences }."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the two traits that matter most: cadences faster than the plan floor are silently raised, and both settings are replaced on every call so omitting cadenceMinutes resets it. These details explain the destructiveHint=true/idempotentHint=true profile in practical terms an agent can act on.

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?

Front-loads the purpose, then the required-parameter constraint, then the two behavioral gotchas, then the return shape. Every sentence carries information the agent needs; there is no filler.

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?

Covers the mutation's side effects, the workspace scoping caveat, the plan-floor clamping, and the returned fields. Even though an output schema exists, the inline return summary removes any need for a follow-up read, which is the right call for a mutation tool.

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 already 100%, so the baseline is 3; the description adds operational meaning by emphasizing that enabled is required on every call and that omitting cadenceMinutes silently resets it, with advice to pass the current value. This overlaps somewhat with the schema's own wording on the plan floor, keeping it short of a 5.

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: turning mention email alerts on/off and setting digest frequency. The scope is precise enough to distinguish it from get_alert_settings, which is named as the read counterpart.

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?

Explicitly routes the agent to get_alert_settings for availableCadences before calling, and advises passing the current cadence when only toggling enabled. It does not spell out when-not-to-use conditions, but the workflow guidance is clear and actionable.

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