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

banca-dati-merito-mcp

Timeline del giudizio

timeline_provvedimento
Read-only

Retrieves the case-history timeline for a legal decision by returning the sequence of linked judgment degrees as displayed in the Banca Dati.

Instructions

Restituisce la sequenza dei gradi di giudizio collegati a un provvedimento, come la mostra la Banca Dati.

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

Input Schema

NameRequiredDescriptionDefault
idYesIdentificativo restituito dalle ricerche.

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 the safety and external-data profile is known. The description adds that the result is the sequence of gradi di giudizio as displayed by the Banca Dati, but it does not describe empty results, ordering, or output shape.

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?

The description is a single, front-loaded sentence with no wasted words. It immediately states the returned resource and scope.

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 a simple read-only lookup with one fully documented parameter and no output schema, the description is mostly complete: it says what is returned and ties it to a provvedimento. Minor gaps remain around result structure and behavior when no linked degrees exist.

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%, and the only parameter 'id' is already documented as the identifier returned by searches. The description does not add further parameter semantics beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: it returns the sequence of litigation levels linked to a provvedimento. This is clearly different from siblings such as leggi_provvedimento or cerca_provvedimenti, but it does not explicitly name an alternative or contrast with one.

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 implied by the phrase 'collegati a un provvedimento': the tool should be used when an agent needs the procedural timeline for a known measure id. However, it gives no explicit when-to-use/when-not-to-use guidance or alternatives such as using leggi_provvedimento for full document content.

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