Skip to main content
Glama

WhatsDownNow

Create outage alerts for a stack

create_alert_stack

START HERE to set up outage alerts for a user. One call, no account or API key. Creates an alert stack that notifies an email address (double opt-in: the recipient clicks one confirmation link) and/or a webhook URL (signed JSON; Slack and Discord incoming-webhook URLs are auto-formatted) when any listed service goes down, stays degraded for N minutes, or gets N user reports in an hour, plus a recovery notice. Services accept slugs or common names ('openai', 'ChatGPT', 'Anthropic', 'AWS', 'Google Cloud'). If the user didn't say where alerts should go, ask for an email or a Slack/Discord webhook URL first. Returns the stack id, a management token and a private manage_link, all shown ONCE: give the user the manage_link and tell them to keep it private.

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": {
      "services": "<services>"
    },
    "name": "create_alert_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLabel, e.g. 'Acme AI production stack'
emailNoEmail address for alerts (recipient must click a confirmation link)
on_downNo
servicesYesServices to watch: slugs or common names, e.g. ['openai', 'stripe', 'cloudflare']
webhook_urlNohttps URL to POST alerts to
notify_recoveryNo
degraded_minutesNoAlert when degraded or down for at least this many minutes; null = off
reports_per_hourNoAlert when user reports in the last hour reach this; null = off

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, open-world, non-idempotent mutation. The description adds substantial operational detail: no account or API key is needed, email uses double opt-in, webhooks receive signed JSON, Slack/Discord URLs are auto-formatted, alert conditions include down/degraded/report thresholds and recovery, and the returned token/manage_link are shown only once.

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?

Front-loads the entry-point instruction, then moves through creation behavior, notification conditions, service-name flexibility, missing-destination guidance, and output handling. It is dense but every sentence carries operational value for a complex create tool.

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 complex mutation tool with no output schema, the description is highly complete: it covers authentication, confirmation flow, webhook signing, alert conditions, accepted service identifiers, prerequisite collection, and how to handle the one-time returned credentials. Minor omissions like explicit idempotency warnings are already covered by annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 75% of parameters, but the description adds meaning beyond it: services accept slugs or common names with examples, email requires confirmation, webhook URLs have special formatting for Slack/Discord, and the conditions map to on_down, degraded_minutes, reports_per_hour, and notify_recovery. It also explains why the agent should collect email or webhook before calling.

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: creates an alert stack for outage alerts. The phrase "START HERE" and the creation-focused wording distinguish it from sibling management tools like get_alert_stack, update_alert_stack, and delete_alert_stack.

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

Usage Guidelines4/5

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

Gives clear context for when to use it as the setup entry point and instructs the agent to first ask for an email or Slack/Discord webhook if no destination was provided. It does not explicitly name alternatives or state when not to use this tool versus update_alert_stack or other siblings.

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.