Skip to main content
Glama
CSOAI-ORG

GDPR Compliance for AI Systems MCP Server

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

rights_request_handler

Guide data subject rights requests under GDPR Articles 15-22, covering access, rectification, erasure, and more with AI-specific steps.

Instructions

Handle data subject rights requests under GDPR Articles 15-22. Provides step-by-step guidance for responding to access, rectification, erasure, restriction, portability, objection, and automated decision-making requests with AI-specific considerations.

Args:
    right_invoked: Which right is being exercised: "access", "rectification", "erasure", "restriction", "portability", "objection", "automated_decision"
    data_subject_description: Description of the requesting data subject
    processing_context: Context of the data processing involved
    ai_system_involved: Whether an AI system processed the data subject's data
    request_details: Specific details of the request
    caller: Caller identifier for rate limiting
    tier: Access tier (free/pro)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
right_invokedYes
data_subject_descriptionYes
processing_contextYes
ai_system_involvedNo
request_detailsNo
callerNoanonymous
tierNofree
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.7/5.0
Behavior2/5

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

No annotations provided. Description does not disclose side effects, auth requirements, rate limits (though caller/tier hints), or what happens to data. Only mentions providing guidance, but behavioral traits beyond that are missing.

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?

Description is concise, front-loaded with purpose, and well-structured with an Args list. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Handles 8 parameters (3 required) with output schema present. Description covers purpose and parameters but lacks usage guidance and behavioral transparency, leaving gaps for an agent to fully understand invocation context.

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 description coverage is 0%, but the description includes an Args section that explains each parameter's purpose (e.g., 'right_invoked: Which right is being exercised'), adding significant meaning beyond the schema which only has titles and types.

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?

Description explicitly states the tool handles data subject rights requests under GDPR Articles 15-22, listing specific rights (access, rectification, erasure, etc.), which clearly distinguishes it from sibling tools like breach_notification or dpia_generator.

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 description implies usage for GDPR DSR handling but does not explicitly state when to use vs not use, nor does it mention alternatives or prerequisites. The step-by-step guidance mention is vague.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/gdpr-compliance-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server