DSGVO.pro — German Digital-Law Compliance

Get Law Article

get-article

Read-onlyIdempotent

Get the full German text of a specific article or paragraph from a law. Returns full text and metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`law`	Yes	The law identifier
`article`	Yes	The article or paragraph number. Letter suffixes are supported and required for norms like "356a" (§356a BGB Widerrufsbutton), "312k", "312j".

Output Schema

TableJSON Schema

Name	Required	Description
`law`	No
`num`	No	Article/paragraph incl. suffix, e.g. "356a"
`text`	No	Full German text of the norm
`unit`	No	"Artikel" (EU regulations) or "Paragraf" (German statutes)
`error`	No	Set instead of the fields above when the norm was not found
`title`	No
`lawName`	No	Full German name of the statute
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Set instead of the fields above when the norm was not found",
+      "type": "string"
+    },
+    "law": {
+      "type": "string"
+    },
+    "lawName": {
+      "description": "Full German name of the statute",
+      "type": "string"
+    },
+    "metadata": {
+      "properties": {
+        "chapter": {
+          "type": [
+            "string",
+            "number",
+            "null"
+          ]
+        },
+        "chapterTitle": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "scannerRelevant": {
+          "description": "Scanner module ids this norm feeds, e.g. [\"widerruf_button\"]",
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "num": {
+      "description": "Article/paragraph incl. suffix, e.g. \"356a\"",
+      "type": "string"
+    },
+    "text": {
+      "description": "Full German text of the norm",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "unit": {
+      "description": "\"Artikel\" (EU regulations) or \"Paragraf\" (German statutes)",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 20, 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=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral context by noting that the content is German text and that the result includes both full text and metadata, going slightly beyond the annotations.

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?

Two short sentences front-load the purpose and result, with no filler or unnecessary repetition of schema details. Every word earns its place.

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?

For a simple 2-param read-only getter with full schema coverage, output schema, and safety annotations, the description is complete enough. It identifies the resource, the language, and the result type, while the sibling list provides surrounding discovery context.

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%, with both parameters fully described in the input schema, including a law enum and article number/suffix guidance. The description adds no additional parameter semantics, so the baseline score of 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?

The description uses a specific verb ('Get') and a specific resource ('full German text of a specific article or paragraph from a law'). It clearly distinguishes itself from sibling tools like list-laws and search-law by targeting a single known norm rather than discovery or enumeration.

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

Usage Guidelines3/5

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

The phrase 'specific article or paragraph' implies the agent should already know which law and article to request, but there is no explicit guidance about when to use this tool versus search-law or list-laws. Usage context is implied rather than clearly stated.

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

All DSGVO.pro — German Digital-Law Compliance tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?