PRIMAMCP

List Available Laws

legal_list_laws

Read-onlyIdempotent

List available laws, regulations, and court decisions in the database. Returns abbreviation, title, source type, jurisdiction, document kind, and version date for each entry.

Unfiltered listings can contain thousands of entries; pass a search term or source_type to keep responses focused. Useful for discovering valid law abbreviations to use as filters in legal_search; legal_get_toc shows a listed law's structure.

Not an existence check for a specific law: EUR-Lex entries store the official long title, so a short name or number can miss a law that is in the corpus. legal_lookup with a citation or legal_search with a topic provides alternative retrieval paths; a missing match does not prove absence from the corpus.

Input Schema

Name	Required	Description
`limit`	No	Max results per page (default 50).
`offset`	No	Start position for pagination.
`search`	No	Case-insensitive search on abbreviation, title and official short designation ('Elektronischer-Rechtsverkehr-Verordnung'), e.g. 'bgb', 'datenschutz'. Also accepts a CELEX number ('32022L2555') or an EU instrument reference ('2022/2555', 'Richtlinie (EU) 2022/2555') and resolves it to the stored law.
`language`	No	Document language: 'de' (documents in German, of every legal order in the scope) or 'en' (currently EDPB/EDSA data-protection guidance only). Omitted, the account's document language applies ('de' unless the account sets another). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English.
`source_type`	No	Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'bgh', 'bpatg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents.
`jurisdiction`	No	Jurisdictions to list, one or more: 'de' (all German law — matches federal AND state law; federal only is source_type='gii'), 'eu', 'de_by' (Bavaria only), 'de_nw' (North Rhine-Westphalia only), 'de_sn' (Saxony only). A value matches its own family only: 'de' adds no EU law. Omitted, the account's legal order applies — for a German account German and EU law.
`document_kind`	No	Filter by document class: the norm subtypes 'statute', 'regulation' and 'directive' form ONE class (any of them lists all three); 'decision' (court case-law), 'guidance' (supervisory-authority soft law, EDSA/DSK) and 'explanatory_memorandum' (legislative materials) are separate classes.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / source_type / anyOf

Previous value: -[
-  {
-    "enum": [
-      "bayern_gesetze",
-      "bverfge",
-      "bverwg",
-      "dsk",
-      "edsa",
-      "eurlex",
-      "eurlex_caselaw",
-      "gesetzesmaterialien",
-      "gii",
-      "nrw_gesetze",
-      "nrw_rechtsprechung",
-      "rechtsprechung",
-      "sachsen_rechtsprechung",
-      "verwaltungsvorschriften"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "bayern_gesetze",
+      "bgh",
+      "bpatg",
+      "bverfge",
+      "bverwg",
+      "dsk",
+      "edsa",
+      "eurlex",
+      "eurlex_caselaw",
+      "gesetzesmaterialien",
+      "gii",
+      "nrw_gesetze",
+      "nrw_rechtsprechung",
+      "rechtsprechung",
+      "sachsen_rechtsprechung",
+      "verwaltungsvorschriften"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / source_type / description

Previous value: -"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."New value: +"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'bgh', 'bpatg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."

Changed4 schema fields changedOct 13, 2026

changedInput schema / properties / jurisdiction / anyOf

Previous value: -[
-  {
-    "description": "Jurisdiction of the legal document.",
-    "enum": [
-      "de",
-      "eu",
-      "de_by",
-      "de_sn",
-      "de_nw"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Jurisdiction of the legal document.",
+      "enum": [
+        "de",
+        "eu",
+        "de_by",
+        "de_sn",
+        "de_nw"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / jurisdiction / description

Previous value: -"Filter by jurisdiction: 'de' (all German law — matches federal AND state law; federal only is source_type='gii'), 'eu', 'de_by' (Bavaria only), 'de_nw' (North Rhine-Westphalia only), 'de_sn' (Saxony only). Empty = no jurisdiction filter."New value: +"Jurisdictions to list, one or more: 'de' (all German law — matches federal AND state law; federal only is source_type='gii'), 'eu', 'de_by' (Bavaria only), 'de_nw' (North Rhine-Westphalia only), 'de_sn' (Saxony only). A value matches its own family only: 'de' adds no EU law. Omitted, the account's legal order applies — for a German account German and EU law."

changedInput schema / properties / language / description

Previous value: -"Document language: 'de' (German-language documents from German and EU sources) or 'en' (currently EDPB/EDSA data-protection guidance only). Omitted, the account's document language applies ('de' unless the account sets another). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."New value: +"Document language: 'de' (documents in German, of every legal order in the scope) or 'en' (currently EDPB/EDSA data-protection guidance only). Omitted, the account's document language applies ('de' unless the account sets another). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."

changedInput schema / properties / source_type / description

Previous value: -"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the DE default only the translated documents."New value: +"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / language / description

Previous value: -"Document language: 'de' (default, German-language documents from German and EU sources) or 'en' (currently EDPB/EDSA data-protection guidance only). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."New value: +"Document language: 'de' (German-language documents from German and EU sources) or 'en' (currently EDPB/EDSA data-protection guidance only). Omitted, the account's document language applies ('de' unless the account sets another). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."

Changed6 schema fields changedSep 21, 2026

changedInput schema / properties / document_kind / anyOf

Previous value: -[
-  {
-    "description": "Legal document type classification.\n\nUses StrEnum so values compare equal to plain strings for\nseamless PostgreSQL/Qdrant compatibility.",
-    "enum": [
-      "statute",
-      "regulation",
-      "directive",
-      "decision",
-      "explanatory_memorandum",
-      "guidance"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Document class: legislation, court decisions, legislative materials or guidance.",
+    "enum": [
+      "statute",
+      "regulation",
+      "directive",
+      "decision",
+      "explanatory_memorandum",
+      "guidance"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / jurisdiction / anyOf

Previous value: -[
-  {
-    "description": "Legal jurisdiction identifiers.\n\nUses StrEnum so values compare equal to plain strings for\nseamless PostgreSQL/Qdrant compatibility.",
-    "enum": [
-      "de",
-      "eu",
-      "de_by",
-      "de_sn",
-      "de_nw"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Jurisdiction of the legal document.",
+    "enum": [
+      "de",
+      "eu",
+      "de_by",
+      "de_sn",
+      "de_nw"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / jurisdiction / description

Previous value: -"Filter by jurisdiction: 'de' (all German law — matches federal AND state law; for federal only use source_type='gii'), 'eu', 'de_by' (Bavaria only), 'de_nw' (North Rhine-Westphalia only), 'de_sn' (Saxony only). Leave empty for all jurisdictions."New value: +"Filter by jurisdiction: 'de' (all German law — matches federal AND state law; federal only is source_type='gii'), 'eu', 'de_by' (Bavaria only), 'de_nw' (North Rhine-Westphalia only), 'de_sn' (Saxony only). Empty = no jurisdiction filter."

changedInput schema / properties / language / anyOf

Previous value: -[
-  {
-    "description": "Content language of legal documents.\n\nUses StrEnum so values compare equal to plain strings for\nseamless PostgreSQL/Qdrant compatibility.",
-    "enum": [
-      "de",
-      "en"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Document language, independent of the language of the answer.",
+    "enum": [
+      "de",
+      "en"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / language / description

Previous value: -"Corpus language: 'de' (default — the full German + EU corpus) or 'en' (English-language corpus: currently EDPB/EDSA data-protection guidance only; much smaller than 'de'). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."New value: +"Document language: 'de' (default, German-language documents from German and EU sources) or 'en' (currently EDPB/EDSA data-protection guidance only). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."

changedInput schema / properties / source_type / anyOf

Previous value: -[
-  {
-    "description": "Known legal document source types.\n\nUses StrEnum so values compare equal to plain strings\n(e.g. ``SourceType.GII == \"gii\"``), which keeps Qdrant\npayloads and PostgreSQL columns compatible without conversion.",
-    "enum": [
-      "gii",
-      "eurlex",
-      "eurlex_caselaw",
-      "rechtsprechung",
-      "sachsen_rechtsprechung",
-      "sachsen_gesetze",
-      "bayern_gesetze",
-      "nrw_gesetze",
-      "nrw_rechtsprechung",
-      "gesetzesmaterialien",
-      "edsa",
-      "bverfge",
-      "bverwg",
-      "verwaltungsvorschriften",
-      "dsk"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "bayern_gesetze",
+      "bverfge",
+      "bverwg",
+      "dsk",
+      "edsa",
+      "eurlex",
+      "eurlex_caselaw",
+      "gesetzesmaterialien",
+      "gii",
+      "nrw_gesetze",
+      "nrw_rechtsprechung",
+      "rechtsprechung",
+      "sachsen_rechtsprechung",
+      "verwaltungsvorschriften"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedSep 8, 2026

changedInput schema / properties / language / description

Previous value: -"Corpus language: 'de' (default — the full German + EU corpus) or 'en' (English-language corpus: currently EDPB/EDSA data-protection guidance only; much smaller than 'de'). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. Set 'en' only when the user explicitly works in English or asks for the English version."New value: +"Corpus language: 'de' (default — the full German + EU corpus) or 'en' (English-language corpus: currently EDPB/EDSA data-protection guidance only; much smaller than 'de'). DE and EN are separate corpora — a document published in both languages has one entry per language under the same abbreviation. 'en' selects the English corpus regardless of the answer language; 'edsa' is published mostly in English."

changedInput schema / properties / source_type / description

Previous value: -"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English — pair it with language='en', or the DE default leaves you only the few translated documents."New value: +"Filter: 'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Note: 'edsa' is published mostly in English: language='en' covers the full set, the DE default only the translated documents."

First observedSep 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description goes further by warning that unfiltered listings can contain thousands of entries and by disclosing that EUR-Lex entries store official long titles, meaning a short-name miss does not prove absence. That negative-result caveat is exactly the behavioral context annotations cannot provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short paragraphs are clearly front-loaded: purpose and return fields, then filtering guidance, then the existence-check caveat. Each sentence carries signal, though the final caveat sentence stacks multiple sibling references and could be trimmed slightly.

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?

An output schema exists, so return values need no explanation, and the description still supplies the volume warning, the negative-result caveat, and the discovery use case. For a zero-required-parameter listing tool with rich sibling surface, nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretive value by tying 'search term' and 'source_type' to the goal of keeping responses focused on a huge corpus. It stops short of explaining the enum interactions (jurisdiction families, language corpora) that the schema itself details, so it is only mildly additive.

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?

States a specific verb and resource ('List available laws, regulations, and court decisions') and enumerates the returned fields, so the agent knows exactly what this returns. It further distinguishes itself from siblings by naming legal_search (filtering) and legal_get_toc (structure), so the agent can tell the tools apart without opening any schema.

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?

Explicitly covers when to use it ('discovering valid law abbreviations to use as filters in legal_search'), when not ('Not an existence check for a specific law'), and the alternatives ('legal_lookup with a citation or legal_search with a topic'). It also gives the practical condition for narrowing ('pass a search term or source_type') when listings are huge.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PRIMAMCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List Available Laws

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources