redreplier

Update Alert Settings

update_alert_settings

Destructive

Manage mention email alerts by turning them on or off and setting the digest interval in minutes. Review current settings to avoid resetting the cadence.

Instructions

Turn mention email alerts on or off and set how often the digest is sent. enabled is required on every call. cadenceMinutes must be one of 15, 30, 60, 120, 180, 240, 720, 1440, otherwise 400 "Invalid alert frequency for your plan"; a value 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, and to confirm the applied cadence after. Returns the resolved settings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`enabled`	Yes	Turn email alerts on or off
`cadenceMinutes`	No	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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The resolved settings after clamping: { enabled, cadenceMinutes, minIntervalMinutes, availableCadences }.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Sep 7, 2026

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 }."

First observedv0.1.0Sep 7, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, it discloses specific side effects: both settings are replaced, omitting cadenceMinutes resets to fastest allowed, values faster than plan floor are silently raised, and validation returns 400. No contradictions with annotations.

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?

Every sentence provides necessary information—purpose, validation rules, side effects, usage guidance, and output. The structure is logical and free of fluff.

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?

The description fully covers what the tool does, how to use it, expected behavior, error conditions, and return value. It also references the appropriate sibling tool for complementary actions, making it self-contained for an agent.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical meaning: allowed cadence values, plan floor behavior, reset semantics when omitted, and requirement that enabled is always passed. This goes well beyond the schema.

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?

The description clearly states the tool's function: turning mention email alerts on/off and setting the digest frequency. It uses a specific verb and distinguishes it from sibling tools like get_alert_settings.

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?

The description explicitly directs users to get_alert_settings for available cadences before and confirmation after, and explains when to use this tool (e.g., passing current value when only toggling enabled).

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