Skip to main content
Glama

Search Legislation

search_legislation

Search Italy's national legislation on Normattiva and European or international legal registries by keyword, statute title, or number; filter by enactment year and limit results.

Instructions

Search Italy (IT) national legislation (statutes, acts, codes, regulations) via Normattiva - Portale della Legge Vigente (normattiva.it) and European/International legal registries.

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": {
      "query": "<query>"
    },
    "name": "search_legislation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional enactment year filter.
limitNoMaximum number of results to return.
queryYesKeywords or statute title/number to search in Italy legislation.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does add useful context by naming the upstream registry (normattiva.it) and the document types searched. It says nothing about whether results are metadata-only or full text, result ordering/ranking, rate limits, or authentication, all of which matter for a search tool with a limit cap. An output schema exists, so return shape need not be described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the jurisdiction and source are stated immediately. Slightly overstuffed with parenthetical synonyms and website names, but every element is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter search tool with an output schema and no annotations, the description covers what is searched and where, but leaves the agent guessing about result nature (full text vs. citation metadata) and about sibling selection. It is adequate but short of what a no-annotation tool needs.

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 documents query, year, and limit including the 1-50 range and default. The description contributes only indirectly, via the enumerated document types that hint at useful query vocabulary. Baseline 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 gives a specific verb (Search) and a specific resource (Italy national legislation), then enumerates the covered document types (statutes, acts, codes, regulations) and names the source (Normattiva). This distinguishes it in substance from search_case_law, though it never says so explicitly, and the trailing 'European/International legal registries' clause blurs whether the scope is Italian-only or multi-jurisdictional.

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 word 'legislation' suggests this is for statutes rather than court decisions, which is enough for an agent to route away from search_case_law. There is no explicit when-to-use, when-not-to-use, or statement of which sibling handles case law, treatises, or citation verification.

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