Skip to main content
Glama

DPIA intake as a Word file

export_dpia_intake
Read-only

Use this when the user wants the DPIA intake of a concrete, intended use of AI or of personal data as a Word file to work on, and, where the FRIA comes into play, the FRIA draft too. It takes the same fixed fact answers as the case check of Praxikon, as coded choices, and gives the same documents as the download on the site: the four parts of Article 35(7) GDPR with the seventeen points of the Dutch government model DPIA, each point filled from the facts given, partly filled, or left as an open question, with articles and source links. Leave out what is not known: it counts as unknown and becomes an open question, never a no. Send only the coded answers and never the case text, names or other personal data; there is no field for them. The answer gives a download_url: the case check on the site with the answers in the part after #, which the browser never sends to the server; opening it shows the outcome and builds the Word file in the user's browser. Give the user that link, the explanation and the summary, and show the notice. Praxikon keeps no copy of the file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_dpia_intake"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNo
langNoLanguage of the document. Dutch is the default.nl
roleNo
scaleNo
domainNo
effectNo
specialNo
aiSystemNo
criminalNo
transferNo
automatedNo
frequencyNo
inServiceNo
profilingNo
interactionNo
apCategoriesNo
personalDataNo
interactionKnownNo
store_for_improvementNoOptional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7.

Output Schema

NameRequiredDescriptionDefault
dateNo
dpiaYes
friaYes
langNo
viewYes
titleYes
noticeYes
storedYes
summaryYesWhat the intake holds, point by point, as plain text to show in the chat.
documentsYes
provenanceYes
explanationYes
fria_reasonNo
download_urlYesThe case check with the answers in the URL fragment; the browser builds the Word file.
fria_includedYes
rules_versionNo
full_check_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / store_for_improvement / description
      Previous value: -"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7."New value: +"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7."
  2. Changed1 schema field changed
    • addedInput schema / properties / store_for_improvement
      Added value: +{
      +  "default": true,
      +  "description": "Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds substantial behavior beyond that: no case text, names or personal data are accepted or transmitted, answers travel in the URL fragment the browser never sends to the server, the Word file is built client-side, and Praxikon keeps no copy. It also explains how omitted answers are treated (unknown becomes an open question, never a no).

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

Conciseness3/5

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

The critical trigger and the download_url handoff are front-loaded and useful, but the body is a dense run-on with repeated privacy statements ('never the case text, names or other personal data' restated as 'keeps no copy'), making it slower to scan than needed.

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?

For a 19-parameter tool with an output schema, the description covers the privacy constraints, the unknown-handling rule, and how to use the returned download_url, so nothing essential is missing. The remaining gap is per-code meaning for the 17 undocumented parameters, which it defers to check_case.

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 only 11% across 19 parameters, so the description must compensate, and it partly does: it states that codes and meanings are identical to check_case input and clarifies that unanswered fields count as unknown rather than no. But it adds nothing per-parameter, and an agent without check_case's schema cannot interpret codes like 'apCategories' or 'interaction' from this text alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a concrete artifact (the DPIA intake as a Word file, plus the FRIA draft where relevant) built from fixed coded answers, and ties it to the same documents as the site download, which implicitly separates it from check_case. It is a long, clause-chained sentence, so the agent has to parse it, but the verb+resource is unmistakable.

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?

It gives an explicit trigger ('Use this when the user wants ... as a Word file to work on') and the input contract (the same coded answers as check_case, omit unknowns), plus post-call instructions to hand over the link, explanation, summary and notice. It never says outright when to prefer check_case instead, leaving the contrast implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources