banca-dati-merito-mcp

Overview Schema Source Related Servers Discussions Admin

Elenca uffici giudiziari

elenca_uffici

Read-only

Lists judicial offices in the Banca Dati grouped by appellate court district, with an optional district filter to return only offices in a specified district.

Instructions

Elenca gli uffici giudiziari presenti nella Banca Dati, raggruppati per distretto di corte d'appello. Con distretto restituisce solo gli uffici di quel distretto.

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

Input Schema

Name	Required	Description	Default
`distretto`	No	Distretto di corte d'appello, per esempio BOLOGNA.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 30, 2026

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 profile is covered. The description adds one behavioral detail beyond them — that results are grouped by court of appeal district — but says nothing about matching semantics for the filter (exact name? case sensitivity?), pagination, or what happens with an unknown district.

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?

Two short sentences with no filler; the default behavior (grouped by district) is front-loaded and the optional filter behavior follows immediately.

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 read-only enumeration tool with one fully documented optional parameter and no output schema, the description covers what the tool returns and how to filter it. Only the fine detail of district-name matching is left implicit, which is a minor gap.

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 coverage is 100% and the single `distretto` parameter is documented with an example (BOLOGNA), so the schema carries the detail. The description only restates that the parameter filters the output to that district, adding little beyond the schema itself.

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 enumerates the judicial offices present in the Banca Dati and says they are grouped by court of appeal district. That is clearly distinguishable from sibling tools such as cerca_provvedimenti or elenca_valori, though it does not name an alternative explicitly.

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?

The second sentence implies usage of the optional filter (pass `distretto` to narrow the result to one district, omit it to list everything), which is helpful context. However, there is no explicit when-to-use versus when-not guidance and no named alternatives among siblings.

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