Skip to main content
Glama

AINumbers Fintech Intelligence Suite

NIS2 ICT Supply-Chain Diligence Scorer (Art. 21(2)(d) / ENISA)

score_nis2_supply_chain_diligence
Read-onlyIdempotent

NIS2 ICT Supply-Chain Diligence Scorer (Art. 21(2)(d) / ENISA): OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Consumes upstream artifacts from: art-144-nis2-incident-significance-scorer. Output feeds: art-146-nis2-governance-readiness-checker. Open at: https://ainumbers.co/chaingraph/art-145-nis2-ict-supply-chain-diligence-scorer.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Score ICT vendor due-diligence posture against NIS2 Art. Outputs: active_risk_flags, enisa_control_coverage_pct, remediation_checklist, risk_score, risk_tier, vendor_incident_history_12mo. Output schema: call describe_tool("score_nis2_supply_chain_diligence").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "score_nis2_supply_chain_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "audit_clause_in_contract": {},
      +  "breach_notification_sla_hours": {},
      +  "data_residency_eu_only": {},
      +  "service_availability_pct": {},
      +  "sub_contractor_count": {},
      +  "vendor_incident_history_12mo": {},
      +  "vendor_iso27001_certified": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "active_risk_flags": {
      -      "type": "array"
      -    },
      -    "enisa_control_coverage_pct": {
      -      "type": "integer"
      -    },
      -    "remediation_checklist": {
      -      "type": "array"
      -    },
      -    "risk_score": {
      -      "type": "integer"
      -    },
      -    "risk_tier": {
      -      "type": "string"
      -    },
      -    "vendor_incident_history_12mo": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "active_risk_flags": {
      +      "type": "array"
      +    },
      +    "enisa_control_coverage_pct": {
      +      "type": "integer"
      +    },
      +    "remediation_checklist": {
      +      "type": "array"
      +    },
      +    "risk_score": {
      +      "type": "integer"
      +    },
      +    "risk_tier": {
      +      "type": "string"
      +    },
      +    "vendor_incident_history_12mo": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real surface beyond them: compute-mode semantics (auto/server/browser, gpu:true always delegating), transient processing with no storage or logging, and AP2 artifact export with execution_hash. What it omits is the numeric thresholds or tolerance behind the risk_score/risk_tier, which would have pushed this to a 5.

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

Conciseness2/5

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

The purpose is front-loaded in the first sentence and the 'Summary:' line, but the middle is bloated with compute-node boilerplate, a full URL, and a 64-character FV-status hash that do not help an agent decide or invoke. Roughly half the text could be cut without loss of decision-relevant information.

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 compensates by listing all six return fields and enumerating the upstream/downstream chain links an agent needs for orchestration. The only gap is that the nested policy_parameters object, which drives the scoring function, is left entirely unexplained.

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%, so the schema already documents compute, parent_hashes, parent_tool_ids, and policy_parameters. The description restates compute modes and chain-parent semantics but adds no field-level meaning, and the nested policy_parameters keys are not elaborated anywhere. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Score ICT vendor due-diligence posture against NIS2 Art. 21(2)(d)' against ENISA controls, and names the six outputs. It is distinguishable from siblings like check_nis2_art21_measures, but the description never explicitly contrasts itself with those siblings, leaving the agent to infer the boundary.

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?

Provides chain context — consumes artifacts from art-144-nis2-incident-significance-scorer and feeds art-146-nis2-governance-readiness-checker — plus the 'use synthetic or anonymised inputs only' constraint. However, it never says when to pick this over sibling NIS2 scorers/checkers, so the selection guidance is implied rather than stated.

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.