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

banca-dati-merito-mcp

Cerca abstract

cerca_abstract
Read-only

Search decision abstracts—summaries of principles—for guidance on a legal issue; filter by text, date, area, or criteria, with unfiltered searches returning recent publications.

Instructions

Cerca gli abstract della Banca Dati, cioè le sintesi dei principi affermati nei provvedimenti. Usalo per gli orientamenti su una questione. Un abstract non è una massima ufficiale: prima di citarlo come principio di un provvedimento, verificalo nel testo con leggi_testo_provvedimento. Senza filtri restituisce gli ultimi pubblicati.

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

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 behavior, so the description's added value is the epistemic warning that an abstract is not an official massima and must be verified in the text, plus the default ordering when no filters are given. That is real context beyond the structured fields, though return shape and pagination limits are left to the schema.

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: purpose, use case, reliability caveat with the exact fallback tool, and default behavior. Front-loaded with the core action and no filler.

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 intent, default behavior, and the critical trust caveat. It does not describe what a result row contains (e.g. how to reach the underlying provvedimento), which would help an agent chain calls, but nothing essential to invocation is missing.

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 82%, with pagination (da, quanti), date field semantics, and criteria values already documented in-schema. The description adds only the implicit default of unfiltered results, so the schema does the heavy lifting and 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 and then defines that resource ("le sintesi dei principi affermati nei provvedimenti"), which lets an agent tell abstracts apart from full decisions. It does not explicitly name cerca_provvedimenti as the alternative for full-text decision search, so sibling differentiation is only partial.

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?

"Usalo per gli orientamenti su una questione" gives a clear use condition, and the caveat routes the agent to leggi_testo_provvedimento for verification. It also states the no-filter default (latest published), but gives no explicit when-not condition against cerca_provvedimenti.

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