Skip to main content
Glama

hu_get_legislation

Read-onlyIdempotent

Fetch metadata for any Hungarian legislation by its ELI (type, year, issuer, serial). Use for decrees and ministerial regulations.

Instructions

Fetch metadata for any Hungarian legislation by its ELI (type + year + issuer + serial).

Use this for anything other than Acts (torveny) - government decrees, ministerial decrees, etc. Use hu_list_doc_types for valid doc_type codes and hu_list_issuers for valid issuer codes (issuer codes are case-sensitive, e.g. Korm for Government).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes4-digit year, e.g. ``"2016"``.
issuerYesNJT issuer code, case-sensitive, e.g. ``"Korm"`` (Government).
serialYesthe document's serial number within that year, e.g. ``"428"``.
doc_typeYesNJT type code, e.g. ``"R"`` (rendelet / decree).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
titleNo
issuerNo
serialNo
eli_uriNo
doc_typeNo
subtitleNo
source_urlNo
dataset_noteNoNemzeti Jogszabalytar (NJT) is Hungary's official, free-to-use national legislation database, maintained by MKIFK (Magyar Kozlonykiado es Igazsagugyi Forditokozpont Zrt.) at njt.jog.gov.hu. Hungary publishes a genuine, documented national ELI (European Legislation Identifier) URI scheme since 2023 (see /eli/urisemak). Each ELI URI resolves (HTTP 302) to a server-rendered HTML document page carrying the consolidated (currently-in-force, unless a historical date is requested) text of the act. There is no REST/JSON API and no headless full-text search - the search/browse UI is an AngularJS SPA that requires a session and JavaScript; documents must be addressed by a known ELI (type + year + serial, and an issuer code for non-Act types).
in_force_dateNo
human_readable_citationNo
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that it returns metadata and notes case-sensitivity of issuer codes, but does not add context like rate limits, pagination, or error behavior. It is consistent with annotations and provides some added detail.

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 two sentences, front-loaded with the primary purpose and followed by usage guidance. No word is wasted; it is efficient and well-structured.

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 output schema exists and annotations are rich, the description adequately explains what the tool does, when to use it, and how to find valid parameter values. It is complete for a simple read-only metadata fetch tool.

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% with each parameter having descriptions and examples. The description adds the conceptual ELI composition ('type + year + issuer + serial') which helps, but does not introduce new parameter semantics beyond what the schema already documents.

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 'Fetch metadata for any Hungarian legislation by its ELI (type + year + issuer + serial)', using a specific verb and resource. It also differentiates from sibling tools by explicitly excluding Acts, which distinguishes it from hu_get_act.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this for anything other than Acts' and directs users to hu_list_doc_types and hu_list_issuers for valid codes. This provides clear when-to-use and when-not-to-use guidance with named alternatives.

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/hu-eli-mcp'

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