norm-mcp

Overview Schema Source Related Servers Discussions Admin

Leggi un URN Normattiva già disponibile

normattiva_leggi_urn

Read-onlyIdempotent

Resolve an Italian legal URN to its full text, verifying that the result is current law and not a preamble, abrogated, or historical version.

Instructions

Legge un URN completo ottenuto altrove. Verifica esito: anche una risposta 200 può essere un preambolo; abrogato e vigenza_storica non sono diritto vigente. Per fonte più articolo usa normattiva_leggi_articolo, che passa dalla tabella verificata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urn`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`urn`	Yes
`esito`	Yes
`testo`	No
`avvisi`	No
`heading`	No
`incipit`	No
`caratteri`	No
`messaggio`	No
`permalink`	Yes
`attribuzione`	Yes
`aggiornamenti`	No
`protezione_rete`	Yes
`vigenza_storica`	No
`data_abrogazione`	No

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"
+  }
+}

changedOutput schema / description

Previous value: -"Un solo schema per i tre esiti possibili (`esito` discrimina), così i\ndue strumenti che leggono un articolo condividono un'unica forma di\nuscita — nessuna copia divergente fra loro."New value: +"Schema comune per articolo, abrogato e preambolo."

addedOutput schema / properties / protezione_rete

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

changedOutput schema / required

Previous value: -[
-  "esito",
-  "urn",
-  "permalink",
-  "attribuzione"
-]New value: +[
+  "esito",
+  "urn",
+  "permalink",
+  "attribuzione",
+  "protezione_rete"
+]

First observedv0.1.1Aug 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds critical runtime caveats: the agent must check `esito`, a 200 response may still be only a preamble, and abrogated or historical-validity results are not current law. These are exactly the kind of behavioral warnings that prevent incorrect interpretation of results.

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?

The description is three concise sentences with no filler. The first sentence states the core operation, the second adds essential result-interpretation guidance, and the third routes to an alternative tool. Every sentence earns its place and the most important information is front-loaded.

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?

Given that this tool has one simple parameter, rich annotations covering read-only/idempotent/non-destructive behavior, and an output schema, the description covers the key operational nuance and sibling routing. It tells the agent what to verify in the response and warns about false positives. Nothing critical is missing for correct invocation.

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?

The schema provides no description for the single `urn` parameter (0% coverage), so the description must compensate. It adds meaningful context by calling the URN 'completo' and specifying that it was 'ottenuto altrove', which differentiates it from source/article inputs. It does not include a URN format example, but for a single simple parameter this is adequate.

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 action, 'Legge un URN completo ottenuto altrove', clearly defining the tool as reading a complete Normattiva URN obtained elsewhere. It also distinguishes itself from the sibling normattiva_leggi_articolo by clarifying that source-plus-article requests belong to that tool. The purpose is unambiguous and well differentiated.

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?

The description explicitly states when this tool is appropriate: when a complete URN is already available. It also gives a concrete alternative, instructing the agent to use normattiva_leggi_articolo for source-plus-article queries because that tool uses the verified table. This is clear direction with a named alternative.

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

Deploy Server