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

banca-dati-merito-mcp

Scarica documento

scarica_documento

Downloads the PDF of an Italian civil decision or abstract to the configured download folder and returns the saved file path, without overwriting existing files.

Instructions

Salva il PDF di un provvedimento o di un abstract nella cartella di download configurata dall'utente (predefinita: Download/banca-dati-merito) e restituisce il percorso del file. Non sovrascrive file esistenti. La Banca Dati può impiegare oltre mezzo minuto a generare il PDF. Per leggere il contenuto usa leggi_testo_provvedimento o leggi_abstract.

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": {
      "tipo": "<tipo>",
      "id": "<id>"
    },
    "name": "scarica_documento"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentificativo restituito dalle ricerche.
tipoYesprovvedimenti (sentenze, ordinanze, decreti) oppure abstract (sintesi dei principi).
nome_fileNoNome del file senza estensione, per esempio 'Trib Bologna 2571-2025'. Predefinito: tipo e id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses that a file is written to a user-configured folder with a concrete default path, that existing files are never overwritten (consistent with idempotentHint=false and destructiveHint=false), that the file path is returned, and that PDF generation can exceed thirty seconds. These are exactly the operational facts an agent needs and none of them are recoverable from the annotations.

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?

Three tight sentences: what it does and where, the overwrite policy, the latency caveat, then the alternative tools. Every sentence carries distinct information with no repetition of the title or name.

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, and the description compensates by stating that the file path is returned. Combined with the latency warning, the non-overwrite policy and the routing to reader tools, nothing an agent needs in order to call this correctly 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 100%, so the schema already explains id, tipo and the nome_file default. The description adds no parameter-level meaning such as how nome_file interacts with the no-overwrite rule, so the baseline of 3 applies.

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 verb and resource: saving the PDF of a provvedimento or abstract to the configured download folder. It also distinguishes itself from the reader siblings by naming leggi_testo_provvedimento and leggi_abstract as the tools for content, so an agent can tell the tools apart without inspecting schemas.

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?

It states the condition that selects this tool (need the PDF file on disk) and explicitly routes content-reading needs to leggi_testo_provvedimento or leggi_abstract. The alternative is named directly rather than left to inference.

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