Skip to main content
Glama

Open an incident by hand

open_incident

Opens an incident for what the checks cannot see: a slow service, a problem a customer reported. With a message it publishes the first update on the status pages that show its monitors (and emails their subscribers on Pro plans); alert pages the monitors' contacts once. It stays open until resolve_incident and never counts as downtime. Every plan, at most 20 open. Free.

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": {
      "title": "<title>"
    },
    "name": "open_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
alertNoAlert the monitors' contacts once, and again when it is resolved. Ask the user first.
stateNoThe first update's state, investigating by default.
titleYesWhat the dashboard, alerts and status pages call it.
messageNoOptional first update for the visitors of the status pages that show the monitors.
severityNoHow serious the problem is.critical
monitor_idsNoThe monitors it affects (GET /monitors): its updates show on the published status pages that show any of them. None or up to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / severity / description
      Added value: +"How serious the problem is."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: publishing the first update to status pages, emailing subscribers on Pro plans, alerting contacts once, staying open until resolve_incident, never counting as downtime, and a 20-open cap per plan. These side-effect, lifecycle, and limit disclosures are exactly what an agent needs for a mutation tool.

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 but front-loaded, with each sentence conveying operational behavior. The final 'Free.' fragment and the phrasing 'Every plan, at most 20 open' are slightly ambiguous or truncated, costing some clarity.

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?

Covers lifecycle, side effects, notification behavior, and plan limits for a mutation tool with no output schema. The return value is not described and the trailing 'Free' is unclear, but the definition is otherwise complete for correct invocation.

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: message publishes a status-page update and can email Pro subscribers, while alert pages the monitors' contacts once. Other parameters such as severity, state, and monitor_ids remain fully documented in the schema.

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 ('Opens an incident') and scopes it to conditions the checks cannot see, such as a slow service or customer-reported problem. This clearly distinguishes manual incident creation from monitor-generated incidents and names resolve_incident as the closing counterpart.

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?

Explicitly frames when to use it—problems invisible to checks—and points to resolve_incident for closure. It does not enumerate when-not-to-use cases or other alternatives, but the 'what the checks cannot see' boundary gives clear guidance.

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.

Resources