Skip to main content
Glama

be_get_act

Read-onlyIdempotent

Fetch metadata for a Belgian act using its ELI coordinates: document type, publication date, and NUMAC identifier.

Instructions

Fetch metadata for a Belgian act by its ELI coordinates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYespublication day, 1-31.
yearYespublication year, e.g. ``2020``.
monthYespublication month, 1-12.
numacYesthe NUMAC identifier (Belgian legislative numbering system), e.g. ``2020040054``.
doc_typeYesone of ``loi``, ``decret``, ``ordonnance``, ``arrete``, ``constitution``.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo
yearNo
monthNo
numacNo
titleNo
eli_uriNo
doc_typeNo
languageNofr
source_urlNo
dataset_noteNoMoniteur Belge / Belgisch Staatsblad (ejustice.just.fgov.be) is Belgium's official gazette, keyless and CC0-licensed. Legislation is addressed by ELI coordinates (type/year/month/day/numac) at /eli/{type}/{yyyy}/{mm}/{dd}/{numac}/justel. There is no free-text search API - only a year-listing page per legislation type (/eli/{type}/{year}) for discovery, and get-by-coordinate for full text. Belgium is trilingual (French/Dutch/German); French is used as the primary human_readable form by LDH convention, but NL and DE renderings exist for most acts.
dossier_numberNo
entry_into_forceNo
publication_dateNo
source_authorityNo
table_of_contentsNo
human_readable_citationNo
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description 'Fetch metadata' is consistent but adds no extra behavioral context (e.g., permissions, limits, or side effects) beyond what annotations provide. The value added is minimal.

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?

Single sentence, front-loaded with the main purpose, no redundant information. Every word earns its place.

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?

The description is short but adequate given the existence of a full output schema and 100% parameter coverage in the schema. It explains what the tool does and how to identify the act. Could be slightly more detailed about the concept of ELI coordinates, but the schema fills the 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 description coverage is 100%, so baseline is 3. The description hints at ELI coordinates but doesn't add new semantic meaning beyond the schema's parameter descriptions (e.g., doc_type enum, date fields, numac). No additional clarification on formats or constraints.

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 specifies the verb 'Fetch', the resource 'metadata for a Belgian act', and the method 'by its ELI coordinates'. It distinguishes from siblings 'be_get_text' (which likely fetches text) and 'be_list_year' (which lists acts by year).

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 provides no guidance on when to use this tool versus alternatives like 'be_get_text' or 'be_list_year'. It only states what it does without indicating prerequisites or exclusion cases.

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

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