Skip to main content
Glama

nis2_criticality_classifier

Read-onlyIdempotent

[Deterministic entity classification. Pure calculation, read-only, side-effect free]. Classifies corporate entities into 'Essential Entity' vs 'Important Entity' under Directive (EU) 2022/2555 (NIS2) based on sector, headcount FTE, and financial turnover/balance sheet thresholds, computing supervisory regime and statutory fine exposure (up to 10M€ or 2% of global turnover). Usage: Use this tool to determine corporate NIS2 scope and governance duties. For penetration testing scope under DORA, use 'tlpt_threat_led_pentest_scope'. Returns: JSON object with { entityCategory: 'ESSENTIAL' | 'IMPORTANT' | 'OUT_OF_SCOPE', supervisoryRegime: string, maxStatutoryFineEur: number, statutoryObligations: 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": {
      "companyName": "<companyName>",
      "sector": "<sector>",
      "totalEmployeesFte": "<totalEmployeesFte>",
      "annualTurnoverEur": "<annualTurnoverEur>"
    },
    "name": "nis2_criticality_classifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYesPrimary statutory sector of activity under NIS2 Annex I and II
companyNameYesCompany or organization legal name
annualTurnoverEurYesAnnual turnover in EUR (e.g. 50000000)
totalEmployeesFteYesFull-time equivalent employee headcount (e.g. 250)
balanceSheetTotalEurNoAnnual balance sheet total in EUR
isSoleNationalProviderOrDnsTldNoWhether company is a critical DNS/TLD registry or sole national provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'pure calculation, read-only, side-effect free' and 'deterministic' largely restate those hints. It adds domain context (statutory fine exposure) but nothing new about operationally relevant behavior such as external lookups, validation failures, or how edge-case entities are handled.

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?

It is front-loaded with a bracketed summary, then Usage and Returns sections, which makes it scannable. The opening bracket mostly repeats the annotations, but the remaining content is dense and earns its place with no filler.

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?

With no output schema, the description usefully enumerates the return object fields (entityCategory, supervisoryRegime, maxStatutoryFineEur, statutoryObligations). It is nearly complete for a stateless calculator, though it omits that the sole-provider/DNS-TLD flag can override size thresholds, a material classification rule.

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 coverage is 100%, including a documented enum for sector, so the schema already carries parameter meaning and the baseline of 3 applies. The description ties sector/headcount/turnover to the classification logic, but does not explain how balanceSheetTotalEur or isSoleNationalProviderOrDnsTld alter the outcome, which is the one place it could have added value.

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 description names a specific verb and resource ('Classifies corporate entities into Essential vs Important under NIS2') and states the exact criteria (sector, FTE, turnover/balance sheet). It is clearly distinguishable from the DORA pen-test sibling named in the usage line.

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?

It gives an explicit when-to-use ('determine corporate NIS2 scope and governance duties') and an explicit routing rule to an alternative ('For penetration testing scope under DORA, use tlpt_threat_led_pentest_scope'). The boundary between the two tools is unambiguous.

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