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

banca-dati-merito-mcp

Leggi abstract

leggi_abstract
Read-only

Retrieve a complete abstract by ID, including title, legal principle, source decision details, linked conforming and nonconforming precedents, and personal notes.

Instructions

Restituisce un abstract completo: titolo, testo del principio, estremi del provvedimento da cui deriva, precedenti conformi e difformi collegati dalla Banca Dati, 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_abstract"
  }
}

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 l'abstract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds genuinely useful context beyond them by detailing the returned payload, including that personal notes and cross-referenced conforming/non-conforming precedents are included. It stops short of noting behavior when the id is missing or how the area/includi_cartelle flags affect retrieval.

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?

A single sentence that leads with the verb and payload, with no rhetorical padding; every clause names a distinct piece of returned content.

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?

There is no output schema, and the description compensates well by enumerating the fields of the returned abstract. It is slightly short on failure behavior and on how area/includi_cartelle modify the result, but an agent can call it correctly from this definition.

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, area (CIVILE-only search results) and includi_cartelle. The description mentions personal notes being returned, which loosely links to includi_cartelle, but adds no syntax or conditional detail beyond the schema.

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 (Restituisce) and resource (un abstract completo) and enumerates exactly what the returned object contains: title, principle text, provision details, linked precedents, personal notes. It clearly reads as a fetch-by-id tool versus the search siblings, though it never names cerca_abstract or cerca_provvedimenti to make the distinction 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 notion of fetching a complete abstract presupposes you already hold an identifier (the schema's id param says 'Identificativo restituito dalle ricerche'). There is no explicit when-to-use versus cerca_abstract/leggi_provvedimento and no stated exclusions or prerequisites.

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