Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HR_ELI_BASE_URLNoBase URL of the Narodne novine official gazettehttps://narodne-novine.nn.hr
HR_ELI_AUDIT_DIRNoDirectory for audit logs of tool calls~/.matematic/audit
HR_ELI_CACHE_DIRNoDirectory for caching fetched documents~/.matematic/cache/hr-eli

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
hr_list_issueA

List the documents published in a Narodne novine gazette issue.

hr_get_actA

Fetch document metadata by ELI coordinate (year + issue + doc).

hr_coverageA

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

hr_get_textA

Fetch the full official HTML text of a document by ELI coordinate.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

hr_get_act and hr_get_text are clearly separated as metadata versus full HTML text, and hr_list_issue handles discovery by gazette issue. hr_coverage is distinct as a meta-tool for gaps. The only minor risk is that hr_get_act and hr_get_text both accept ELI coordinates, but their descriptions resolve the boundary.

Naming Consistency4/5

Tools share a consistent hr_ prefix and mostly follow a verb_noun pattern: hr_list_issue, hr_get_act, hr_get_text. hr_coverage breaks the pattern by using a noun-only name, though it is still understandable and consistent in style.

Tool Count5/5

Four tools is an appropriate, focused scope for an ELI legal document connector. Each tool performs a distinct retrieval or coverage function, and none feel redundant or missing as a core operation.

Completeness4/5

The server covers the core workflow: discovering documents by issue, fetching metadata, and retrieving full text. A full-text or title search is absent, but hr_coverage explicitly documents known gaps and fallback sources, which mitigates the limitation.

Maintenance

ActivityMaintained
ResponsivenessNo issues