Skip to main content
Glama

build_gdpr_dpia

Build a GDPR Article 35 DPIA and Article 30 RoPA report from processing activities and VAOS receipts, flagging high-residual-risk activities for Article 36 prior consultation.

Instructions

Build a GDPR Article 35 DPIA + Article 30 RoPA report from operator-declared processing activities + a VAOS receipt set. Returns Markdown ready for the DPO + supervisory authority. High-residual-risk activities automatically flagged for Article 36 prior consultation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "controller": "<controller>",
      "activities": "<activities>",
      "risks": "<risks>",
      "receipts": "<receipts>"
    },
    "name": "build_gdpr_dpia"
  }
}

Input Schema

NameRequiredDescriptionDefault
risksYesMap of activity id → risk assessment (necessityProportionality, risks[], mitigations[], residualRisk, priorConsultationRequired). Activities without an entry are auto-flagged as high-risk.
receiptsYesVAOS receipts.
activitiesYesArray of ProcessingActivity records per Article 30(1): id, name, purpose, dataSubjectCategories, dataCategories, specialCategories, recipients, transfers, retention, securityMeasures, legalBasis.
controllerYesControllerIdentity: name, address, email, dpoName, dpoEmail, euRepresentative.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two non-obvious behaviors: the output is Markdown aimed at a DPO/supervisory authority, and high-residual-risk activities are automatically escalated to Article 36 prior consultation. It says nothing about whether anything is persisted or written to disk, or what happens on malformed receipts, which matters for a tool with no 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?

Three sentences, each earning its place: verb+artifact first, output format second, escalation behavior third. No filler and the most decision-relevant information is front-loaded.

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 four-parameter nested-input tool with no output schema, the description adequately covers what is produced (Markdown DPIA + RoPA) and one key output behavior (Article 36 flagging). It is slightly short on whether output is returned only or also persisted, but the schema carries the input contract fully.

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 all four parameters (including the nested risks map and its auto-flag semantics) are already documented. The description only restates the input sources at a high level and adds no syntax, format, or ID-matching detail beyond the schema.

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 (Build) and two precisely named artifacts (GDPR Article 35 DPIA + Article 30 RoPA report), plus the inputs it derives them from. Among siblings that all follow a build_*_compliance pattern, the Article numbers make it immediately distinguishable from build_annex_iv, build_iso_42001, and the rest.

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 input context ('operator-declared processing activities + a VAOS receipt set') implies when the tool applies, but there is no explicit when-to-use, no exclusions, and no routing guidance versus the many sibling compliance-report builders. An agent must infer that a GDPR DPIA (not Annex IV or ISO 42001) is the right artifact.

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