Skip to main content
Glama

gdpr_cross_border_transfer_audit

Read-onlyIdempotent

[Deterministic GDPR Chapter V / Schrems II transfer audit. Pure statutory audit, read-only, side-effect free]. Evaluates international transfers of personal data outside the EEA under GDPR Articles 44-49, auditing adequacy decisions (including EU-US Data Privacy Framework), Standard Contractual Clauses (SCCs), Transfer Impact Assessment (TIA) requirements, and supplementary technical safeguards. Usage: Use this tool to audit cross-border SaaS, cloud infrastructure (AWS/GCP/Azure/Hetzner), and vendor transfers under Schrems II. Returns: JSON object with { isThirdCountryTransfer: boolean, destinationCountryCode: string, transferLawful: boolean, adequacyDecisionActive: boolean, transferMechanism: string, tiaRequired: boolean, supplementarySafeguardsStatus: object, riskScore: number, recommendations: array, legalCitation: string }.

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": {
      "destinationCountryCode": "<destinationCountryCode>"
    },
    "name": "gdpr_cross_border_transfer_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
isEeaCountryNoWhether destination is an EEA Member State
hasAdequacyDecisionNoWhether recipient country has an active adequacy decision under Art. 45
dataSensitivityLevelNoClassification level of transferred personal data
transferMechanismUsedNoContractual transfer tool relied upon under Chapter V GDPR
destinationCountryCodeYes2-letter ISO country code of data recipient (e.g. US, CH, UK, IN, CN)
supplementaryMeasuresImplementedNoWhether technical safeguards (end-to-end encryption with EU sovereign key management) are enforced
transferImpactAssessmentCompletedNoWhether a Transfer Impact Assessment (TIA) has been executed under Schrems II
isUsRecipientDataPrivacyFrameworkCertifiedNoWhether US recipient is certified under EU-US Data Privacy Framework

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'pure statutory audit, read-only, side-effect free' plus the useful property that the result is deterministic. Because no output schema exists, the enumerated JSON return fields (riskScore, legalCitation, recommendations, etc.) add real value about what the caller receives. It does not cover edge cases such as missing optional inputs or how riskScore is derived, keeping it below 5.

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?

The three-part structure (bracketed scope note, Usage, Returns) is front-loaded and scannable, with no filler sentences. The bracketed preamble partially restates the annotation-declared read-only nature, which is slightly redundant, but the overall density is appropriate for a compliance audit tool.

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 an 8-parameter, single-required-parameter audit tool with no output schema, the definition covers scope, usage context, and the full return payload, which is what an agent needs to call it and interpret the result. Minor gaps remain on how optional inputs are defaulted and how conflicting inputs are resolved, but nothing essential is missing.

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 all eight parameters documented, including enum meanings for dataSensitivityLevel and transferMechanismUsed, so the schema does the heavy lifting. The description adds no per-parameter meaning beyond the schema, such as how omitted optional booleans are inferred or what happens when transferMechanismUsed contradicts hasAdequacyDecision. Baseline 3 is appropriate.

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 states a specific verb and resource — evaluating international transfers of personal data outside the EEA under GDPR Articles 44-49 — and enumerates the concrete mechanisms audited (adequacy decisions, SCCs, TIA, supplementary safeguards). It is clearly distinguishable from siblings like ai_act_risk_tier_classifier or gdpr_cmp_tracker_audit by naming the Chapter V transfer scope and Schrems II framing.

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?

The 'Usage:' sentence gives concrete when-to-use context (cross-border SaaS, AWS/GCP/Azure/Hetzner, vendor transfers under Schrems II), which is enough for an agent to route correctly. It stops short of an explicit exclusion or a named alternative tool for non-transfer GDPR questions, so it is not a full 5.

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