Skip to main content
Glama

incident_severity_triage

Read-onlyIdempotent

[Deterministic cyber incident triage. Pure calculation, read-only, side-effect free]. Evaluates operational and security incidents against regulatory materiality thresholds under DORA (JC 2023 83) and NIS2 Article 23: client impact count, downtime duration, economic loss, data compromise, and cross-border Member State impact, triggering statutory 4-hour initial and 24-hour formal notification deadlines. Usage: Use this tool immediately upon discovering an ICT disruption to assess whether mandatory regulatory reporting to CSIRT/National Competent Authorities is required. Do NOT use for penetration test scoping (use 'tlpt_threat_led_pentest_scope'). Returns: JSON object with { isMajorIncident: boolean, notificationRequired: boolean, initialNotificationDeadlineHours: number, formalNotificationDeadlineHours: number, applicableRegimes: string[], triggeredCriteria: string[] }.

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": {
      "incidentSummary": "<incidentSummary>",
      "affectedService": "<affectedService>",
      "durationMinutes": "<durationMinutes>",
      "estimatedClientsAffected": "<estimatedClientsAffected>",
      "dataBreachOrIntegrityLoss": "<dataBreachOrIntegrityLoss>",
      "isCrossBorderEuImpact": "<isCrossBorderEuImpact>",
      "criticalServiceUnavailable": "<criticalServiceUnavailable>"
    },
    "name": "incident_severity_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
affectedServiceYesName of affected financial/ICT service or system
durationMinutesYesDowntime duration in minutes
incidentSummaryYesBrief description of incident impact and symptoms
isCrossBorderEuImpactYesWhether 2 or more EU Member States are impacted
estimatedDirectLossEurNoEstimated direct financial loss in EUR
estimatedClientsAffectedYesEstimated count of affected users/clients
dataBreachOrIntegrityLossYesWhether unapproved data modification or breach occurred
criticalServiceUnavailableYesWhether a critical financial function was disrupted
percentageOfClientsAffectedNoPercentage of active client base affected (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces rather than contradicts them while adding a determinism guarantee ('Pure calculation, side-effect free'). It also discloses the statutory deadlines that drive behavior (4-hour initial, 24-hour formal). It does not discuss input validation or failure modes, but for a pure calculation with full annotation coverage that is a minor gap.

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?

Front-loaded bracketed tag, then purpose, then explicit 'Usage:' and 'Returns:' sections — easy to scan. Slight redundancy in 'Pure calculation, read-only, side-effect free' overlapping the annotations, but no sentence is wasted.

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 9-parameter tool with no output schema, the description compensates by inlining the exact return shape (isMajorIncident, notificationRequired, deadline hours, applicableRegimes, triggeredCriteria). An agent has everything needed to call it and interpret the result.

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 goes further by naming which criteria the inputs feed (client impact count, downtime duration, economic loss, data compromise, cross-border Member State impact), telling the agent why these values matter rather than merely what to pass. It does not explain how thresholds are weighted or how percentageOfClientsAffected interacts with estimatedClientsAffected.

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: deterministic triage of ICT incidents against DORA (JC 2023 83) and NIS2 Article 23 materiality thresholds, naming the exact criteria evaluated. It also explicitly separates itself from 'tlpt_threat_led_pentest_scope', so an agent can distinguish it without opening sibling schemas.

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 an explicit trigger ('immediately upon discovering an ICT disruption') and an explicit exclusion ('Do NOT use for penetration test scoping'), including the alternate tool by name. The decision rule for invoking this versus the named alternative is fully spelled out.

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