norm-mcp

Overview Schema Source Related Servers Discussions Admin

Costruisci la citazione Markdown di un articolo

normattiva_link

Read-onlyIdempotent

Generate a Markdown permalink to an Italian legal article on Normattiva, with optional API verification to confirm the URN resolves correctly.

Instructions

Costruisce [testo](permalink) senza il testo integrale. Per difetto verifica=true consulta l'API: il permalink può rispondere 200 anche a un URN sbagliato. verifica=false è locale e non prova esistenza o vigenza; restituisce comunque lo stato locale di protezione. Non ignorare avvisi su abrogato o preambolo.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fonte`	Yes
`vigenza`	No
`articolo`	Yes
`verifica`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`avvisi`	No
`avviso`	No
`markdown`	Yes
`verificato`	Yes
`protezione_rete`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 5, 2026

addedOutput schema / $defs

Added value: +{
+  "ProtezioneReteOutput": {
+    "description": "Stato corrente e operazioni distinte, incluso un recupero storico.",
+    "properties": {
+      "acquisita_il": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Acquisita Il"
+      },
+      "attivita": {
+        "title": "Attivita",
+        "type": "string"
+      },
+      "avviso": {
+        "title": "Avviso",
+        "type": "string"
+      },
+      "consumo_attivita": {
+        "title": "Consumo Attivita",
+        "type": "string"
+      },
+      "consumo_globale": {
+        "title": "Consumo Globale",
+        "type": "string"
+      },
+      "cooldown_fino": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Cooldown Fino"
+      },
+      "livello": {
+        "title": "Livello",
+        "type": "string"
+      },
+      "origine": {
+        "title": "Origine",
+        "type": "string"
+      },
+      "rapporti": {
+        "items": {
+          "$ref": "#/$defs/RapportoReteOutput"
+        },
+        "title": "Rapporti",
+        "type": "array"
+      },
+      "richieste_residue": {
+        "title": "Richieste Residue",
+        "type": "integer"
+      },
+      "ultimo_incidente": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Ultimo Incidente"
+      }
+    },
+    "required": [
+      "origine",
+      "attivita",
+      "consumo_attivita",
+      "consumo_globale",
+      "richieste_residue",
+      "livello",
+      "avviso"
+    ],
+    "title": "ProtezioneReteOutput",
+    "type": "object"
+  },
+  "RapportoReteOutput": {
+    "description": "Parte serializzabile del rapporto SQLite, senza dati di ricerca.",
+    "properties": {
+      "acquisita_il": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Acquisita Il"
+      },
+      "attivita": {
+        "title": "Attivita",
+        "type": "string"
+      },
+      "avviso": {
+        "title": "Avviso",
+        "type": "string"
+      },
+      "consumo_attivita": {
+        "title": "Consumo Attivita",
+        "type": "string"
+      },
+      "consumo_globale": {
+        "title": "Consumo Globale",
+        "type": "string"
+      },
+      "cooldown_fino": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Cooldown Fino"
+      },
+      "livello": {
+        "title": "Livello",
+        "type": "string"
+      },
+      "origine": {
+        "title": "Origine",
+        "type": "string"
+      },
+      "richieste_residue": {
+        "title": "Richieste Residue",
+        "type": "integer"
+      },
+      "ultimo_incidente": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Ultimo Incidente"
+      }
+    },
+    "required": [
+      "origine",
+      "attivita",
+      "consumo_attivita",
+      "consumo_globale",
+      "richieste_residue",
+      "livello",
+      "avviso"
+    ],
+    "title": "RapportoReteOutput",
+    "type": "object"
+  }
+}

addedOutput schema / properties / avvisi

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Avvisi",
+  "type": "array"
+}

addedOutput schema / properties / protezione_rete

Added value: +{
+  "$ref": "#/$defs/ProtezioneReteOutput"
+}

changedOutput schema / required

Previous value: -[
-  "markdown",
-  "verificato"
-]New value: +[
+  "markdown",
+  "verificato",
+  "protezione_rete"
+]

First observedv0.1.1Aug 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark the tool as read-only and idempotent. The description adds meaningful behavioral detail: verifica=true calls the API and can return 200 for wrong URNs, verifica=false is local and does not prove existence or validity, and warnings about repealed acts or preambles must not be ignored.

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 dense sentences with no filler. The core purpose is front-loaded, verification behavior is explained next, and the operational warning closes the description efficiently.

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?

The output schema covers return values, and the description supplies the most important caveats: false 200 responses, local versus API verification, and warning handling. A small gap remains around the expected formats for fonte, articolo, and vigenza, but the overall picture is sufficient for an agent.

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 0%, so the description must compensate. It thoroughly explains the verifica parameter and its default behavior, but it leaves fonte, articolo, and vigenza to be inferred from their titles and domain knowledge.

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 opens with a specific verb and resource: it 'Costruisce [testo](permalink)' without including full text. This clearly distinguishes the tool from siblings like normattiva_leggi_articolo, which presumably retrieves article content.

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?

The description makes the context clear: use this tool when you need a Markdown citation link, not the full article text. It does not explicitly name sibling alternatives or state when not to use it, but the scope is evident.

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

Deploy Server