PRIMAMCP

Browse Law Table of Contents

legal_get_toc

Read-onlyIdempotent

Get the table of contents of a specific law or court decision. Returns norm keys (e.g. '§ 1', 'Art. 3'), titles, and chapter headings in document order.

Gives the overview of a law's structure; a returned norm_id feeds legal_get_context for the full text. Paginated for large laws.

Input Schema

Name	Required	Description
`limit`	No	Max entries per page (default 100).
`offset`	No	Start position for pagination.
`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	'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'bgh', 'bpatg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents.
`jurisdiction`	No	Legal orders the law must belong to, one or more ('de', 'eu', 'de_by', 'de_nw', 'de_sn'; 'de' matches federal AND state law). Omitted, every legal order answers, and where the abbreviation names laws of several, the account's legal order decides; jurisdiction_scope names it.
`law_abbreviation`	Yes	Law abbreviation, e.g. 'bgb', 'dsgvo', 'stgb'.

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: -"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."New value: +"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'bgh', 'bpatg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / jurisdiction

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "description": "Jurisdiction of the legal document.",
+        "enum": [
+          "de",
+          "eu",
+          "de_by",
+          "de_sn",
+          "de_nw"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Legal orders the law must belong to, one or more ('de', 'eu', 'de_by', 'de_nw', 'de_sn'; 'de' matches federal AND state law). Omitted, every legal order answers, and where the abbreviation names laws of several, the account's legal order decides; jurisdiction_scope names it."
+}

Changed2 schema fields changedOct 13, 2026

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: -"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the DE default only the translated documents."New value: +"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the German corpus only the translated documents."

Changed2 schema fields 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."

changedInput schema / properties / law_abbreviation / maxLength
```
Previous value: -128New value: +512
```

Changed4 schema fields changedSep 21, 2026

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"
+  }
+]

changedInput schema / properties / source_type / description

Previous value: -"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Leave empty to auto-detect; where an abbreviation names a law in two sources, the answer lists them so you can retry. Note: 'edsa' is published mostly in English: language='en' covers the full set, the DE default only the translated documents."New value: +"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Empty = auto-detect; where an abbreviation names a law in two sources, the answer lists both. Note: 'edsa' is published mostly in English: language='en' covers the full set, the DE default only the translated documents."

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: -"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Leave empty to auto-detect; where an abbreviation names a law in two sources, the answer lists them so you can retry. 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: +"'gii', 'eurlex', 'eurlex_caselaw', 'rechtsprechung', 'bverfge', 'bverwg', 'sachsen_rechtsprechung', 'nrw_rechtsprechung', 'bayern_gesetze', 'nrw_gesetze', 'verwaltungsvorschriften', 'edsa', 'dsk' or 'gesetzesmaterialien'. Leave empty to auto-detect; where an abbreviation names a law in two sources, the answer lists them so you can retry. 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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description only needs to add context. It does: the response is paginated for large laws and the entries come back in document order, which is real behavioral information beyond the annotation set.

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 sentences, front-loaded with purpose before returns and routing. 'Gives the overview of a law's structure' partially restates 'table of contents' but carries the routing payload, so the slight redundancy is tolerable.

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?

With an output schema present and 100% parameter coverage, the description need not spell out return values or param formats; it covers purpose, output shape at a high level, pagination and the follow-up call. Only error/empty-result behavior is unaddressed, which is minor for a read-only browse tool.

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 documents law_abbreviation, language, source_type, jurisdiction, limit and offset in detail. The description's note that results are 'paginated for large laws' only loosely gestures at limit/offset and adds no new semantic detail, so the baseline 3 applies.

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 ('Get the table of contents of a specific law or court decision') and immediately clarifies the artifact returned (norm keys, titles, chapter headings in document order). It also positions itself relative to legal_get_context, so an agent can tell it apart from the full-text sibling.

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

Usage Guidelines4/5

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

Explicitly frames the use case ('Gives the overview of a law's structure') and names the follow-up tool plus the payload that connects them ('a returned norm_id feeds legal_get_context for the full text'). It lacks an explicit when-not or a comparison against other listing tools like legal_list_laws, so it falls short of a 5.

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.

Browse Law Table of Contents

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources