Skip to main content
Glama

hu_get_act

Read-onlyIdempotent

Retrieve official metadata for a Hungarian Act by specifying its year and serial number. Use ELI identifiers to access verified legal information from Hungary's legislation database.

Instructions

Fetch metadata for a Hungarian Act (torveny) by its ELI (year + serial).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes4-digit year, e.g. ``"2013"``.
serialYesthe Act's serial number within that year, e.g. ``"5"`` (2013. evi V. torveny is Act no. 5 of 2013, the Hungarian Civil Code).

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 provide readOnlyHint, idempotentHint, and destructiveHint=false, covering key behavioral traits. The description adds no additional context (e.g., return format, auth, rate limits) but is fully consistent with the annotations, earning a neutral score.

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 redundant words. It efficiently conveys the tool's purpose and identifier format.

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 simple tool complexity, full input schema, output schema presence, and comprehensive annotations, the description is complete enough for correct invocation. It states the purpose clearly and does not need to explain return values or safety, as those are covered by other structured fields.

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 fully documents the year and serial parameters. The description's mention of ELI provides a small clarifying connection but does not meaningfully extend parameter semantics.

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 states a specific verb+resource+identifier: 'Fetch metadata for a Hungarian Act (torveny) by its ELI (year + serial)'. It clearly distinguishes from siblings like hu_get_text by focusing on metadata rather than content.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as hu_get_text or hu_get_legislation. It does not mention prerequisites, exclusions, or alternative tools, leaving usage only implied.

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