Skip to main content
Glama

NovaPixel LexGrid

nis2_criticality_classifier

Deterministic entity classification under Directive (EU) 2022/2555 (NIS2) into Essential vs Important Entity, supervisory regime and statutory fine exposure.

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
sectorYes
companyNameYesCompany or organization name
annualTurnoverEurYesAnnual turnover in EUR
totalEmployeesFteYesFull-time equivalent employees
balanceSheetTotalEurNoBalance sheet total in EUR
isSoleNationalProviderOrDnsTldNoWhether company is a critical DNS/TLD or sole national provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The word 'Deterministic' usefully signals that identical inputs yield identical outputs and implies a pure computation with no side effects, and the description lists what the result contains (entity class, supervisory regime, fine exposure). However, it says nothing about jurisdiction limits, what happens with ambiguous or borderline inputs, or whether any data is persisted.

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 the framework and outcome front-loaded and no filler. It is efficient, though the heavy noun stacking ('supervisory regime and statutory fine exposure') packs several outputs into one clause that would read better split.

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

Completeness3/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 does helpfully enumerate the result dimensions (classification, supervisory regime, fine exposure). But for a six-parameter regulatory classification tool it omits the decision logic context and edge-case handling, leaving gaps an agent would want before trusting the result.

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 83%, so the schema already explains most parameters including the sector enum and the critical DNS/TLD flag. The description adds no meaning beyond the schema — it does not explain which inputs drive Essential vs Important status (e.g. employee/turnover thresholds) or how balanceSheetTotalEur is used.

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 verb and resource ('Deterministic entity classification') and specifies the legal framework (Directive (EU) 2022/2555, NIS2) and the resulting categories (Essential vs Important Entity). It is clear about what the tool produces, though it does not name or contrast itself with the sibling tools such as dora_third_party_risk or incident_severity_triage.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned. An agent must infer from 'classification under NIS2' that this applies only to EU-scope entity scoping decisions, with no stated prerequisites or exclusions.

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