Skip to main content
Glama

NovaPixel LexGrid

incident_severity_triage

RTS threshold triage under DORA and NIS2 Art. 23 for major cyber incidents: client impact, duration, financial loss and 4h/24h regulatory reporting deadlines.

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
durationMinutesYesDowntime duration in minutes
incidentSummaryYesBrief description of incident
isCrossBorderEuImpactYesWhether 2 or more EU Member States are affected
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves the key questions open: whether this is a pure read-only assessment or records/files an incident, whether anything is persisted, and what the caller receives. The mention of 4h/24h regulatory deadlines is genuinely useful domain context about urgency, but it is the only behavioral signal present.

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?

A single dense sentence with no filler; every clause (RTS thresholds, DORA/NIS2 Art. 23, impact factors, reporting deadlines) earns its place. It is grammatically a noun phrase rather than a verb-led statement, which slightly weakens front-loading of the action.

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

Completeness2/5

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

With nine parameters, seven required, no annotations and no output schema, the description should say what the tool returns (a severity/triage verdict, reportability determination, deadline) and what makes an incident 'major'. Neither is covered, so an agent knows the topic but not the outcome or the decision logic.

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

Parameters3/5

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

Schema description coverage is 100% across all nine parameters, so the schema already explains each field's meaning and units. The description adds modest value by grouping client impact, duration and financial loss as the assessed dimensions, but it gives no threshold values or units beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific activity and domain: RTS threshold triage of major cyber incidents under DORA and NIS2 Art. 23, with the assessed factors (client impact, duration, financial loss) and the 4h/24h reporting deadlines. That is far more than a restatement of the name, but it never names an alternative, so an agent cannot tell from the text how this differs from sibling nis2_criticality_classifier.

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

Usage Guidelines3/5

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

Usage is only implied via the qualifier 'for major cyber incidents', which tells the agent the input should be a significant incident. There is no explicit when/when-not, no prerequisite stated (e.g. whether triage must follow classification), and no routing to or away from the sibling tools.

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