Skip to main content
Glama

update_alert

Modify an alert's threshold, evaluation window, notification channels, name, or enabled flag. Alert type cannot be updated—create a new alert to change it.

Instructions

Update an existing alert's settings (PATCH /v1/alerts/:id). alertType (the watched metric type) is immutable — to change it, create a new alert and then delete the old one (completing the alert lifecycle). Threshold / evaluation window / notification channels / name / enabled flag / composite conditions can be partially updated (all fields optional). Example phrasing: "lower the monthly budget alert threshold from $100 to $50" / "add Slack as a notification channel".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name of the alert (1-100 chars, no line breaks). Omit to keep the current value
alertIdYesTarget alert ID (from list_alerts)
enabledNoAlert enabled flag. false pauses evaluation (unlike silence, re-enabling requires another PATCH)
conditionsNoUpdate of the v1.5 multi-condition alert. When specified, the single-metric path is ignored in favor of AND/OR aggregation. Can overwrite either an existing single-metric or multi-condition alert.
filterModelNoTarget model (substring match). Omit to keep the current value; pass an explicit null to reset to all models
channelKindsNoNotification channel kinds to enable. Omit to keep the current value. Updating together with channelTargets is recommended
sleepMinutesNoSuppression window for repeated notifications (minutes, 5-10080). Omit to keep the current value
windowMinutesNoAggregation window (minutes, 5-43200). Omit to keep the current value
channelTargetsNoDestination object for every kind listed in channelKinds. Omit to keep the current value
filterProviderNoTarget provider. Omit to keep the current value; pass an explicit null to reset to all providers
thresholdValueNoThreshold (>= 0). Omit to keep the current value
Behavior5/5

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

With no annotations, the description fully discloses behavior: PATCH method, partial updates (all fields optional), enabled flag behavior (pauses vs. silence), and conditions override behavior. Covers mutation safety and lifecycle.

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?

Concise single paragraph (~70 words) front-loading the verb+resource, then key constraints, then examples. No wasted words, efficient structure.

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 all critical aspects: what updates, what is immutable, optionality, field behaviors, and example usage. Given 11 parameters and nested objects without output schema, this is complete and actionable.

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% with detailed descriptions. The description adds value by highlighting immutability of alertType, optionality of all fields, and the conditions override. While schema is already strong, the description provides context beyond 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 it updates an existing alert's settings, identifies the immutable alertType, and lists mutable fields. It distinguishes from sibling tools like create_alert and delete_alert by specifying the update lifecycle.

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?

Provides explicit guidance: alertType is immutable, instructing to create a new alert and delete the old one. Offers example phrasing for typical use cases like lowering a threshold or adding a notification channel.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/argosvix/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server