Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

create_trigger

Set up an alert trigger to notify selected channels when severities, sources, or scopes match; recovery alerts are included by default. Scope filters need Personal edition.

Instructions

Create a new alert trigger, notifying recoveries by default. 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": {
      "name": "<name>",
      "filter_severities": "<filter_severities>",
      "filter_sources": "<filter_sources>",
      "filter_scopes": "<filter_scopes>",
      "channel_ids": "<channel_ids>"
    },
    "name": "create_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add two genuinely useful facts beyond the schema: recovery notifications are relayed by default and scope filters are edition-gated. It says nothing about what the call returns, whether the trigger is immediately active, or what happens if channel IDs are invalid.

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?

Two short sentences with no filler, and the core action is front-loaded before the two caveats. Every clause carries information.

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 7-parameter creation tool with no annotations and no output schema, the description covers the action and two constraints but omits what the call returns (e.g. the new trigger ID) and any preconditions around notification channels. The fully documented schema compensates for most parameter gaps, leaving the description adequate but thin.

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%, so the schema already documents all seven parameters including defaults and CSV formats; baseline is 3. The description's only added semantic is tying scope filters to the Personal edition, which complements the schema's 'advanced filters capability' note but does not extend beyond it.

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?

The description states a specific verb and resource ('Create a new alert trigger'), which cleanly separates it from update_trigger, delete_trigger, list_triggers and get_trigger in the sibling set. It stops short of naming those siblings, so differentiation comes from the verb rather than explicit routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to create a trigger versus updating an existing one, or what a trigger requires to be useful. The only usage-adjacent statement is an edition prerequisite for scope filters ('Scope filters require the Personal edition'), which is a constraint rather than a when-to-use rule.

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