ClevSec EU compliance tools

NIS2 remediation plan (ClevSec Pro)

nis2_remediation_plan

Read-onlyIdempotent

Use after nis2_gap_assessment when the user wants a plan to close their NIS2 gaps. Turns the same answers into every gap with a recommended action, a priority, the NIS2 article and a 30/60/90-day roadmap (governance, risk and incident gaps first). Requires ClevSec Pro.

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": {
      "answers": "<answers>"
    },
    "name": "nis2_remediation_plan"
  }
}

Input Schema

Name	Required	Description	Default
`answers`	Yes	Question id to answer, e.g. {"g1": "yes", "r2": "partial"}. Omit to get the questions. Unanswered questions count as gaps.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-structured context: the plan requires ClevSec Pro and prioritizes governance, risk, and incident gaps first, which affects how the agent should interpret ordering.

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?

Two sentences, front-loaded with the usage trigger, then the output content and a licensing constraint. No filler; every clause carries information.

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?

Although there is no output schema, the description enumerates what the plan contains (gap, action, priority, article, roadmap) and discloses the Pro prerequisite. Nothing needed to select or invoke the tool is missing.

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. The description adds real meaning by stating it consumes 'the same answers' as nis2_gap_assessment, clarifying that the answers object is the shared question-id map rather than a new input format.

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 and output set: every gap with a recommended action, priority, NIS2 article, and a 30/60/90-day roadmap. It also distinguishes itself from the sibling nis2_gap_assessment by positioning itself as the downstream planning step.

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

Usage Guidelines4/5

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

Gives explicit sequencing ('Use after nis2_gap_assessment when the user wants a plan to close their NIS2 gaps'), which tells the agent the triggering condition and prerequisite. No when-not guidance or named alternatives among the other *_remediation_plan siblings, so it falls short of a 5.

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

All ClevSec EU compliance tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?