Skip to main content
Glama

Update an alert

update_alert
Idempotent

Pause/resume a saved target or select email/RSS. Resume only matches future transcriptions; pause drops queued unsent alerts. Following cadence wins. Needs account scope. Free.

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": {
      "id": "<id>"
    },
    "name": "update_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
alertNo
pausedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds real value on top: resume only matches future transcriptions and pause drops queued unsent alerts, which is a data-loss side effect an agent must know before calling. 'Following cadence wins' hints at parameter precedence but is too terse to be actionable, and 'Free' is billing context of marginal use at call time.

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?

Four short sentences, front-loaded with the core action and immediately followed by the risky side effects. Some fragments ('Following cadence wins.', 'Free.') read as notes rather than complete guidance, costing a little clarity for their compactness.

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

Completeness3/5

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

For a three-parameter mutation tool with no output schema and zero schema descriptions, the definition covers the important behavioral risks but leaves the `alert` enum semantics and the combined paused+cadence case underspecified. Adequate to attempt a correct call, not fully complete.

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 0%, so the description carries the burden. It clarifies `paused` well via the resume/pause side effects, but `id` is never mentioned and the `alert` enum (daily/weekly/rss) is described only as 'email/RSS', leaving the daily vs weekly distinction and the paused-vs-cadence interaction unresolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific operations on a specific resource: pause/resume a saved target and choose a cadence/RSS delivery. An agent can tell this mutates an existing alert. It loses a point for calling the alert a 'saved target' and for the imprecise 'select email/RSS' phrasing, which does not map cleanly onto the actual enum values.

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?

Usage is implied rather than stated: pause/resume semantics are given, and 'Needs account scope' flags a prerequisite. There is no explicit guidance on when to use this versus save_alert, remove_alert, or list_saved_alerts, and no statement of what cannot be updated here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources