Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

update_trigger

Modify an existing alert trigger's name, enabled state, notification channels, and severity/source/scope filters. Changes overwrite prior values; scope filters require the Personal edition.

Instructions

Update an existing alert trigger (last-write-wins). Scope filters require the Personal edition.

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": "<name>",
      "filter_severities": "<filter_severities>",
      "filter_sources": "<filter_sources>",
      "filter_scopes": "<filter_scopes>",
      "channel_ids": "<channel_ids>"
    },
    "name": "update_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTrigger ID to update
nameYesTrigger name (1-120 chars)
enabledNoWhether the trigger is active. Defaults to true on creation; omitted on update, the current value is kept.
channel_idsYesNotification channel IDs (at least one required)
filter_scopesYesCSV scope filter (e.g. 'container:42,endpoint:7'). Needs the advanced filters capability. Empty matches everything.
filter_sourcesYesCSV source filter (e.g. 'container,endpoint'). Empty matches everything.
filter_severitiesYesCSV severity filter (e.g. 'critical,warning'). Empty matches everything.
notify_on_resolveNoRelay recovery (resolved) notifications, default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: last-write-wins concurrency semantics and the edition requirement for scope filters. It omits important mutation behavior — whether unspecified required fields overwrite existing values, permission requirements, and error behavior — so it is partial rather than thorough.

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?

Two tight clauses with the core action front-loaded and the constraint second; no filler. Slightly clipped to the point that the edition note reads as an unexplained caveat, but overall efficient.

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 6-required-parameter mutation tool with no annotations and no output schema, the schema covers defaults well, but the description never addresses full-replacement semantics or what a successful call returns/changes. Adequate but with clear gaps for an agent reasoning about side effects.

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 100%, including CSV formats, defaults, and 'empty matches everything', so the baseline of 3 applies. The description adds only the edition caveat tied to filter_scopes and no other parameter-level meaning beyond the schema.

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 a specific verb+resource ('Update an existing alert trigger'), which cleanly separates it from create_trigger, delete_trigger, and get_trigger in the sibling list. It doesn't go further to distinguish from update_channel/update_escalation_policy, but the resource noun does that implicitly.

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 by the name and the '(last-write-wins)' parenthetical, and the Personal-edition constraint on scope filters is a genuine gating note. However, there is no explicit when-to-use guidance, no mention of prerequisites (an existing trigger id), and no statement of what to use instead for partial/field-level edits.

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

Deploy Server

Other Tools