Skip to main content
Glama

Incident: open and start the clocks

incident_open

Open a security or operations incident. Privi starts the notification clocks for the rules you pick (GDPR 72 hours, NIS2 24 hours / 72 hours / one month, SEC four business days, your contract's hours) and writes the incident to your tamper-evident 'incidents' log. Requires the organization API key.

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>",
      "severity": "<severity>",
      "actor": "<actor>"
    },
    "name": "incident_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesWho is doing this (person or agent)
titleYesWhat happened, in a sentence
regimesNoNotification rules that may apply: gdpr = EU GDPR Article 33 (personal data breach); nis2 = EU NIS2 Article 23 (significant incident); sec_8k = US SEC Form 8-K Item 1.05 (material cybersecurity incident)
aware_atNoWhen you became aware (ISO 8601). Default: now
severityYeslow|medium|high|critical
material_atNoSEC only: when you decided the incident was material
contract_hoursNoHours your customer contracts give you to notify them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive operation; the description adds real context beyond that: clock side effects (GDPR 72h, NIS2 24h/72h/one month, SEC four business days, contract hours), tamper-evident log writing, and an API-key auth requirement. It does not warn that repeat calls are not idempotent (i.e. re-opening may create a second incident) or describe what is returned, which keeps it from 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?

Three front-loaded sentences with no filler: purpose, effects, prerequisite. The middle sentence is dense with a nested parenthetical of statutory deadlines, which slows reading slightly but every clause carries information an agent needs.

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?

For a 7-parameter mutation tool with no output schema, the description covers purpose, side effects, auth and regime deadlines well. The main omission is the return value (presumably an incident identifier) and duplicate-open behavior, which an agent would need since no output schema exists.

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; the description adds value by tying the regimes parameter to actual deadlines per framework and noting that contract_hours is your customer-contract notification window. That clarifies intent rather than merely restating field names, though it does not add format guidance (e.g. ISO 8601 for aware_at) beyond 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?

The first sentence states a specific verb and resource ('Open a security or operations incident'), and the second sentence spells out the two concrete effects: starting notification clocks for the chosen regimes and appending to the tamper-evident 'incidents' log. Against siblings like incident_close, incident_update and incident_status, the 'open' action is unambiguously distinguished.

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?

Clear context for when to call it (opening a security or operations incident) plus a stated prerequisite ('Requires the organization API key') and an explanation of what the regimes parameter drives. It does not say when not to use it or explicitly route to incident_update/incident_close, so it falls short of full alternative-routing 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