Skip to main content
Glama
banca-dati-merito-mcp

banca-dati-merito-mcp

Cerca provvedimenti

cerca_provvedimenti
Read-only

Search Italian civil court decisions by full text, field criteria, and dates, or list recently published rulings with metadata, excerpts, and linked abstracts.

Instructions

Cerca sentenze, ordinanze e decreti di merito nella Banca Dati, per testo, criteri di campo e date. Senza filtri restituisce gli ultimi pubblicati. Restituisce estremi, metadati, estratti evidenziati e gli abstract collegati. Gli estratti sono frammenti: non bastano per dire che cosa ha deciso un provvedimento. Prima di riferire il principio o l'esito di un provvedimento, leggine il testo con leggi_testo_provvedimento.

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": "cerca_provvedimenti"
  }
}

Input Schema

NameRequiredDescriptionDefault
daNoPosizione del primo risultato, per sfogliare (0 = dal primo).
areaNoArea della Banca Dati. Le ricerche oggi restituiscono risultati solo in CIVILE; le statistiche contano anche PENALE.CIVILE
dateNo
testoNoRicerca nel testo.
ordineNodesc
quantiNoQuanti risultati restituire (predefinito 20, massimo 50).
criteriNoCondizioni sui campi, combinate in AND.
escludiNoCondizioni da escludere (AND NOT).
ordina_perNoPredefinito: rilevanza se c'è un testo, altrimenti data_pubblicazione.
note_personaliNoCerca nelle note personali dell'utente.
solo_cartelle_personaliNoLimita ai documenti salvati nelle cartelle personali dell'utente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world nature, yet the description still adds real behavioural content: default ordering, the fact that excerpts are highlighted fragments, and that abstracts are linked rather than embedded. The explicit warning that fragments are insufficient to determine the outcome is valuable beyond any structured field.

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?

Four short sentences with zero filler: capability, default behaviour, return shape, then the reliability caveat and the escape hatch. The most decision-relevant constraint (don't report holdings from excerpts) lands before the reader stops reading.

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?

For an 11-parameter tool with nested objects and no output schema, the description covers what is returned (estremi, metadati, estratti, abstract) and the main usage trap. It leans on the schema for field-level detail, which is appropriate given 82% coverage.

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 high (82%), including enum meanings and paging semantics, so the schema carries most parameter meaning. The description only adds that search works by text, field criteria and dates; it says nothing extra about quanti/da paging limits or the criteria-vs-escludi split. Baseline 3 applies.

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 (search judgments, orders and decrees in the Banca Dati) plus the three search axes: text, field criteria and dates. It also declares the no-filter default (latest published) and what is returned. It differentiates from leggi_testo_provvedimento but not from near neighbours such as cerca_abstract or cerca_valori.

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 clear operating context: without filters it returns the most recently published items, and it explicitly routes the agent to leggi_testo_provvedimento before asserting what a decision held. It does not say when to prefer this over cerca_abstract or when field criteria should come from risolvi_criteri (that is only in the schema).

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