Skip to main content
Glama
Ansvar-Systems

Finnish Law MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_legislationA

Search Finnish statutes and regulations by keyword.

Searches provision text using FTS5 with BM25 ranking. Supports boolean operators (AND, OR, NOT), phrase search ("exact phrase"), and prefix matching (term*).

Returns matched provisions with snippets, relevance scores, and document metadata.

When NOT to use: If you already know the exact statute number and provision, use get_provision instead. If you need a comprehensive multi-source answer, use build_legal_stance.

get_provisionA

Retrieve a specific provision from a Finnish statute.

Specify the statute number and either chapter+section or provision_ref directly. Examples:

  • document_id="1050/2018", chapter="1", section="1" → 1 luku 1 §

  • document_id="1050/2018", provision_ref="1:1" → same result

  • document_id="434/2003", section="6" → 6 § (flat lookup)

Omit chapter/section/provision_ref to get all provisions in the statute.

When NOT to use: If you are searching by keyword and don't know the exact statute/provision, use search_legislation instead.

search_case_lawA

Search Finnish court decisions (oikeustapaukset).

Searches case summaries and keywords. Filter by court (KKO, KHO, hovioikeus, etc.) and date range.

When NOT to use: If you need statute text, use search_legislation. Case law searches only cover court decisions.

get_preparatory_worksA

Get preparatory works (esityöt) for a Finnish statute.

Returns linked government proposals (HE), committee reports, and related documents with summaries. Essential for understanding legislative intent behind statutory provisions.

When NOT to use: If you need the statute text itself, use get_provision. Preparatory works explain legislative intent, not current law.

validate_citationA

Validate a Finnish legal citation against the database.

Parses the citation, checks that the document and provision exist, and returns warnings about status (repealed, amended). This is the zero-hallucination enforcer.

Supported formats:

  • "Laki 1050/2018 1 luku 1 §"

  • "1050/2018 1:1"

  • "SFS 2018:218 1 kap. 1 §" (legacy compatibility)

  • "Prop. 2017/18:105"

  • "SOU 2017:39"

  • "NJA 2020 s. 45"

When NOT to use: If you want to format a citation string, use format_citation. This tool checks existence in the database.

build_legal_stanceA

Build a comprehensive set of citations for a legal question.

Searches across statutes, case law, and preparatory works simultaneously to aggregate relevant citations. Use this for broad legal research questions.

When NOT to use: If you need a specific provision or targeted search, use get_provision or search_legislation instead.

format_citationA

Format a Finnish legal citation per standard conventions.

Formats:

  • full: "Laki 1050/2018 3 luku 5 §"

  • short: "1050/2018 3:5"

  • pinpoint: "3 luku 5 §"

When NOT to use: If you want to check whether a citation exists in the database, use validate_citation instead.

check_currencyA

Check if a Finnish statute or provision is in force (current or historical).

Returns the document's status (in_force, amended, repealed, not_yet_in_force), dates, and warnings. Provide as_of_date for historical evaluation.

When NOT to use: If you need the actual text of a provision, use get_provision. This tool only checks status.

get_eu_basisA

Get EU legal basis (directives and regulations) for a Finnish statute.

Returns all EU directives and regulations that this statute implements, supplements, or references. Includes reference types, article citations, and whether each EU document is a primary implementation.

Essential for understanding which EU law a Finnish statute is based on.

When NOT to use: For provision-level EU references, use get_provision_eu_basis. To find Finnish laws implementing EU law, use get_finnish_implementations.

get_finnish_implementationsA

Find Finnish statutes implementing a specific EU directive or regulation.

Given an EU document ID (e.g., "regulation:2016/679" for GDPR), returns all Finnish statutes that implement, supplement, or reference it. Shows implementation status and which articles are referenced.

Essential for finding Finnish law corresponding to EU requirements.

When NOT to use: If you have a Finnish statute and want its EU basis, use get_eu_basis (opposite direction).

search_eu_implementationsA

Search for EU directives and regulations with Finnish implementation information.

Search by keyword, type, year range, or community. Returns matching EU documents with counts of Finnish statutes referencing them.

Use this for exploratory searches like "data protection" or "privacy" to find relevant EU law.

When NOT to use: If you already know the EU document ID, use get_finnish_implementations for direct lookup.

get_provision_eu_basisA

Get EU legal basis for a specific provision within a Finnish statute.

Returns EU directives/regulations that a specific provision implements or references, with article-level precision. For example, DSL 2:1 references GDPR Article 6.1.c.

Use this for pinpoint EU compliance checks at the provision level.

When NOT to use: For statute-level EU references (not a specific provision), use get_eu_basis instead.

validate_eu_complianceA

Validate EU compliance status for a Finnish statute or provision.

Checks for:

  • References to repealed EU directives (e.g., Data Protection Directive 95/46/EC)

  • Missing implementation status

  • Outdated references

Returns compliance status (compliant, partial, unclear, not_applicable) with warnings and recommendations.

Note: This is Phase 1 validation. Full compliance checking against EU requirements will be added in future phases.

When NOT to use: For basic EU reference lookup, use get_eu_basis. This tool assesses compliance status.

aboutA

Server metadata, dataset statistics, freshness, and provenance. Call this to verify data coverage, currency, and content basis before relying on results.

list_sourcesA

List all authoritative data sources used by this server, including provider, license, coverage, and freshness metadata. Call this to understand where the data comes from.

get_provision_at_dateA

Retrieve Finnish statute provision text as it read on a specific date (time-travel query).

This tool enables historical legal research by showing how a provision was worded at any point in time, accounting for all amendments since original enactment.

Use cases:

  • "What did Tietosuojalaki 1:3 say in 2019?"

  • "Show me Rikoslaki 3:1 before the 2019 amendment"

  • "Was this provision in force on 2020-06-15?"

Supports:

  • Historical versions (any date in the past)

  • Current version (today's date)

  • Future provisions (enacted but not yet in force)

Returns the complete provision text, validity dates, and optionally the amendment history showing what changed after the queried date.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Case Law StatisticsMetadata about case law data freshness and coverage

TDQS

A4.2/5.0

Scored across 16 tools

Disambiguation5/5

Each tool targets a distinct resource and action: validation, searching, retrieval, formatting, status checks, EU lookups, and metadata. Potential overlaps like validate_citation vs check_currency are clearly differentiated by input and purpose, and get_eu_basis vs get_provision_eu_basis are scoped by statute vs provision.

Naming Consistency4/5

The vast majority of tools follow a consistent snake_case verb_noun pattern (search_legislation, get_provision, validate_eu_compliance). The single exception is 'about', which breaks the pattern, and get_provision_at_date has an extra preposition, though still clear.

Tool Count4/5

16 tools is on the higher end of reasonable for a legal research server that spans statutes, case law, preparatory works, EU implementations, citation handling, and compliance. Each tool serves a distinct purpose, so the count feels justified rather than bloated.

Completeness4/5

The server covers core workflows comprehensively: searching, retrieving, validating, formatting, historical versions, and EU compliance. A notable gap is the lack of a direct tool to fetch a full court decision text (only search_case_law with summaries and keywords), which agents may need for deep case analysis.