Skip to main content
Glama

it_cassazione_search

Read-onlyIdempotent

Search live Italian Supreme Court decisions via the official SentenzeWeb engine, matching full-text queries against OCR'd decision text. Filter by year, chamber, and sub-chamber.

Instructions

Full-text search of Corte di Cassazione (Supreme Court) decisions, live.

Queries SentenzeWeb (the Court's own free public search engine) in real time - no local index. Free-text search matches the decision body (ocr).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annoNooptional 4-digit year filter (decision year, e.g. "2021").
limitNomax hits (1..100).
queryYessearch terms, matched as a phrase against the decision text.
chamberNooptional, "civile" (civil) or "penale" (criminal).
sub_chamberNooptional, "lavoro" (Labour) or "tributaria" (Tax) - both are sub-chambers of the civil section.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNo
queryYes
total_foundYes
dataset_noteNoSource: Corte Suprema di Cassazione, SentenzeWeb (live public Solr search, italgiure.giustizia.it/sncass) - full OCR text, 420K+ decisions (civil + criminal, including the Labour and Tax sub-chambers). Italian Open Data License (IODL 2.0), no authentication. This is NOT the subscription-gated ItalgiureWeb full-database search used by the judiciary; it is the Court's own free public search engine, queried live on every call (no local index to build or refresh).
total_returnedYes
Behavior4/5

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

The description adds behavioral context beyond the annotations: it performs live queries to an external public engine, does not use a local index, and matches decision body text (OCR), implying potential OCR errors. These details are not captured by the readOnly/openWorld/idempotent hints.

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 concise and front-loaded: the first sentence states the core purpose, and the second elaborates with essential behavioral details. Every sentence earns its place with no 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?

Given the strong annotations and full parameter schema coverage, the description sufficiently covers purpose, live external query behavior, and OCR search scope. An output schema exists, so return-value documentation is not needed. The description is complete for a search tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that free-text search matches the OCR'd decision body, complementing the schema's 'decision text' phrase and giving context about what is searched.

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 clearly states the tool's function: full-text search of Corte di Cassazione decisions. It specifies the resource (Supreme Court decisions), the action (search), and distinguishes it from siblings by noting it queries the live external SentenzeWeb engine rather than a local index.

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 description implies usage context—'live' and 'no local index' suggest this is for real-time queries—but it does not explicitly state when to prefer this tool over alternatives like it_case_search or it_cassazione_get. No exclusions or alternative naming are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matematicsolutions/it-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server