Skip to main content
Glama

Update application alert

update_application_alert
Destructive

Change one of an Application's own alerts (own=true in list_application_alerts): its name, environment, condition and the places it sends to are replaced by what this call sends, so send every one of them, reading the current values with list_application_alerts first; severity is kept when left out. What the evaluator recorded on the alert is kept. An organisation rule listed beside the application's alerts is refused: change it with the organisation alert tools. Needs alerts.manage, or applications.write on the application.

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": {
      "application_id": "<application_id>",
      "alert_id": "<alert_id>",
      "environment_id": "<environment_id>",
      "name": "<name>",
      "condition": "<condition>",
      "send_to": "<send_to>"
    },
    "name": "update_application_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe alert's name, 1 to 100 characters, for example 'Failed requests'. In the organisation's alert list it reads '<application> · <environment> · <name>'.
send_toYesThe ids of 1 to 5 places the alert sends to, as list_alert_destinations returns them, each named once.
alert_idYesThe alert's id (alert_id), as list_application_alerts returns it. Only an alert with own=true is the application's to change or remove.
severityNoThe alert's severity. On a create it defaults to warning; on an update leaving it out keeps the alert's severity.
conditionYesWhen the alert fires: the reading of metric stays above threshold for hold_minutes.
application_idYesThe Application's id.
environment_idYesThe id of the environment the alert watches: one of the application's environments (get_application_configuration lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, and the description adds real substance on top: fields are replaced rather than merged ("send every one of them"), severity is preserved when omitted, evaluator-recorded state is untouched, and organisation-owned alerts are rejected. The main remaining gap is that it does not say what the response contains or whether the replacement is reversible.

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?

Front-loaded with the core action and the critical replace-everything warning, with no filler sentences. It is noticeably dense and clauses are chained with semicolons, which is efficient but slows parsing slightly.

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?

For a destructive, permissioned mutation with a nested condition object and 7 parameters, the definition covers semantics, prerequisites, refusal behavior and sibling routing. No output schema exists, but the description does not need one to be callable correctly here.

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%, so the baseline is 3, but the description adds replace-vs-merge semantics for send_to, environment_id and condition that the schema alone does not convey — an agent would otherwise assume a partial patch. The severity-omitted behavior is repeated from the schema but reinforces it usefully.

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 one of an Application's own alerts") and immediately scopes it with the discriminator "own=true in list_application_alerts", which separates it from organisation-level alert tools. The list of mutable fields (name, environment, condition, send_to) makes the tool's surface unambiguous.

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?

Explicitly says to read current values with list_application_alerts first, and names the exclusion case: an organisation rule listed beside the application's alerts is refused and must be changed with the organisation alert tools. It also names the required permissions (alerts.manage or applications.write), so an agent knows both the precondition and the alternative path.

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.