Skip to main content
Glama

NIS2 readiness quickscan

nis2_quickscan
Read-onlyIdempotent

Compute a NIS2 Article 21.2 readiness score for a domain by mapping the IntoDNS quickscan onto the ten NIS2 measures. Returns a 0-100 weighted total, per-measure status (Article 21.2 a-j), evidence rows, critical gaps, and concrete fix…

Instructions

Compute a NIS2 Article 21.2 readiness score for a domain by mapping the IntoDNS quickscan onto the ten NIS2 measures. Returns a 0-100 weighted total, per-measure status (Article 21.2 a-j), evidence rows, critical gaps, and concrete fix suggestions. The score reflects only the DNS and email layer of NIS2 — full NIS2 compliance also requires audit of web applications, supply chain, organisational processes, and training. Use when the user asks about NIS2 compliance, NIS2 readiness, NIS2 Article 21.2, cyber-hygiene compliance, or related EU-NIS regulation checks for a domain.

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": {
      "domain": "<domain>"
    },
    "name": "nis2_quickscan"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for the standard caveat text shown alongside the score.en
domainYesDomain name only, e.g. example.com (no URL, path, or port)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com"New value: +"Domain name only, e.g. example.com (no URL, path, or port)"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive operation, and the description goes well beyond that by disclosing the return shape (0-100 weighted total, per-measure a-j status, evidence rows, gaps, fixes) and a significant limitation: it covers only the DNS and email layer of NIS2.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each carrying distinct payload: what it does, what it returns, and what its limitations/triggers are. The capability statement is front-loaded and no sentence is filler.

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?

With no output schema, the description compensates by enumerating the returned fields and the per-measure status range. Combined with the explicit scope caveat and clear trigger conditions, an agent has everything needed to call it and to set user expectations correctly.

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%, so both parameters (domain, lang) are already documented in the schema, including the enum and default for lang. The description adds only that the score is computed 'for a domain' and says nothing about domain format or language handling 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?

States a specific verb (compute) and resource (NIS2 Article 21.2 readiness score) plus the mechanism (mapping IntoDNS quickscan onto the ten measures). No sibling tool covers NIS2 scoring, and the scope boundary to the DNS/email layer makes its niche unmistakable.

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?

Explicitly lists trigger phrases: NIS2 compliance, NIS2 readiness, Article 21.2, cyber-hygiene compliance, and EU-NIS regulation checks for a domain. The added caveat that full NIS2 compliance needs other audits effectively tells the agent when this tool alone is insufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.