norm-mcp

Overview Schema Source Related Servers Discussions Admin

Cerca una fonte nella tabella verificata

normattiva_trova_fonte

Read-onlyIdempotent

Search legal sources by name or alias for type, date, number, attachment, and status offline. Use before historical codes: a guessed attachment can point to a different act; absence is not conclusive.

Instructions

Cerca nome o alias nella tabella locale: tipo, data, numero, allegato e stato, senza rete. Usalo prima di un codice storico: un allegato indovinato può puntare a un atto diverso. Una fonte assente qui non è assente dall'ordinamento.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`testo`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`nota`	No
`tipo`	No
`alias`	No
`stato`	No
`numero`	No
`trovata`	Yes
`allegato`	No
`nota_stato`	No
`disponibile`	No
`nome_canonico`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.2.0Sep 5, 2026
- addedOutput schema / properties / disponibile / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedOutput schema / properties / disponibile / default
```
Previous value: -trueNew value: +null
```
- removedOutput schema / properties / disponibile / type
```
Removed value: -"boolean"
```
First observedv0.1.1Aug 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: the tool searches only a local table without network access, and it cautions that the local table is not a complete representation of the legal order. This helps the agent calibrate expectations about result completeness.

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 sentences, each earning its place: first defines the action and scope, second gives usage guidance with rationale, third states a critical limitation. It is front-loaded with the core purpose and contains no 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?

For a simple one-parameter tool with an output schema and annotations covering safety, the description is complete. It covers what the tool does, its offline/local scope, when to use it, what caveats apply to the result, and the meaning of the sole parameter. Nothing essential 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 0%, so the description carries the burden. It compensates by indicating that the 'testo' parameter is the 'nome o alias' to search for in the local table. While it does not provide format examples or edge cases, it gives the essential semantic meaning for the single parameter.

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 states a specific verb ('Cerca') and resource ('tabella locale'), and lists the searchable attributes: 'tipo, data, numero, allegato e stato'. It distinguishes the tool from network-based siblings by explicitly noting it works 'senza rete', making its offline nature clear.

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 gives explicit usage context: 'Usalo prima di un codice storico' and warns that 'un allegato indovinato può puntare a un atto diverso'. It also provides a clear limitation ('Una fonte assente qui non è assente dall'ordinamento') which functions as when-not-to-conclude absence. It does not name sibling alternatives, but the context is sufficient.

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

Deploy Server