Skip to main content
Glama

Alert Rules

alterlab_alert_rule
Destructive

Manage alert rules that notify you by email, webhook or Slack when your account crosses a threshold (credit balance, domain or product failure rate, response-time spike, failed schedules, stuck runs). action=create needs name, alert_type and conditions; list returns your rules; get, update (PATCH, only the fields you send), delete and test take rule_id (test sends a sample alert through the rule's channels); history lists fired alerts. Use alterlab_monitor instead to watch a page for content changes. Cloud export, extraction templates, org and API key management, BYOK and workflow definitions have no MCP tool: they are dashboard/API only.

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": {
      "action": "<action>"
    },
    "name": "alterlab_alert_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate, update: rule name
limitNohistory: page size. Default 50
actionYescreate, list, get, update, delete, test or history
offsetNohistory: rows to skip. Default 0
rule_idNoget, update, delete, test: alert rule ID. history: optional filter
channelsNocreate, update: delivery channels {email: bool, webhook_id: str, slack_webhook_url: str}. Default {email: true}
is_activeNoupdate: enable or disable the rule
alert_typeNocreate: what the rule watches. list, history: optional filter
conditionsNocreate, update: thresholds for the alert_type, e.g. {threshold_microcents: 1000000} for credit_threshold or {failure_rate_pct: 50, window_minutes: 60} for domain_failure_rate
domain_filterNocreate, update: limit the rule to these domains
cooldown_minutesNocreate, update: minutes before the rule can fire again. Default 60
include_inactiveNolist: include disabled rules. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond destructiveHint=true it discloses that update is a PATCH applying only the fields sent, and that test actually sends a sample alert through the rule's real channels — an external side effect an agent must not trigger casually. It does not say whether delete is reversible or what permissions are required, so not a 5.

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?

Dense and front-loaded: trigger scope first, then per-action requirements, then the alternative tool. The trailing sentence about dashboard-only features is marginally relevant to tool selection but reads slightly like a changelog note; the whole thing is a single long paragraph rather than structured per action.

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

Completeness4/5

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

Seven actions, 12 parameters and nested objects are handled well — each action's required inputs and behavior are addressed, and the alternative-tool boundary is covered. With no output schema, it would help to say what list/get/history return (shape, pagination via limit/offset), which is the main remaining gap.

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 cross-parameter meaning the schema does not: which parameters each action consumes, that conditions are keyed to the chosen alert_type, and that rule_id doubles as an optional history filter. This helps map an intent to the right parameter set.

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+resource ('Manage alert rules') and immediately enumerates the trigger types it watches (credit balance, failure rate, response-time spike, stuck runs). It also names the exact action set, so an agent can distinguish it from sibling tools like alterlab_monitor without opening the schema.

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?

Gives explicit routing: 'Use alterlab_monitor instead to watch a page for content changes' rules out the closest-looking alternative, and it also states which capabilities have no MCP tool (cloud export, extraction templates, org/API key management, BYOK, workflow definitions). Each action's prerequisite is spelled out (create needs name/alert_type/conditions; rule_id for get/update/delete/test).

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.