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

banca-dati-merito-mcp

Leggi provvedimento

leggi_provvedimento
Read-only

Retrieves full metadata for an Italian civil decision by ID from Banca Dati di Merito, including judges, subject, legal references, outcome, abstracts, related decisions, and personal notes.

Instructions

Restituisce i metadati completi di un provvedimento: estremi, giudici, materia, parole chiave, riferimenti normativi, esito, gli abstract che ne derivano, i provvedimenti precedente e successivo nel giudizio, e le note personali dell'utente.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "leggi_provvedimento"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificativo restituito dalle ricerche.
areaNoArea della Banca Dati. Le ricerche oggi restituiscono risultati solo in CIVILE; le statistiche contano anche PENALE.CIVILE
includi_cartelleNoAggiunge le cartelle personali dell'utente che contengono il provvedimento.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful disclosure about what content is returned (including 'note personali dell'utente' and adjacent provvedimenti in the same giudizio), which hints at scope expansion, but says nothing about the effect of includi_cartelle or about data-access implications of pulling personal notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the return scope enumerated; dense but every clause carries information about the payload. Slightly list-heavy, but no filler or redundancy.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it does so thoroughly: estremi, giudici, materia, parole chiave, riferimenti normativi, esito, abstract, prev/next provvedimento, personal notes. Combined with full schema coverage and read-only annotations, an agent has enough to call it correctly.

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 100%, so both optional parameters (area, includi_cartelle) are already documented with defaults and caveats. The description adds no parameter-level meaning beyond implying the tool works on a single 'provvedimento'; 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 (returns complete metadata of a provvedimento) and enumerates exactly which metadata fields come back, which implicitly separates it from siblings like leggi_testo_provvedimento or leggi_abstract. It never names those siblings, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the schema note 'Identificativo restituito dalle ricerche' suggests the flow search-then-read, but the description itself gives no when-to-use guidance and no routing (e.g., 'use leggi_testo_provvedimento for the full text'). The agent must infer the alternative from the field list.

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