Skip to main content
Glama

movahedi.ca Privacy Data

Look up consequential privacy actions

canadian_privacy_consequential_action_lookup_v1
Read-onlyIdempotent

Look up the twelve consequential actions in the Canadian privacy corpus v2026.12.1: the moments where an AI agent handling personal information can cause real legal harm (vendor onboarding, cross-border transfer, breach notification, automated decisions, trackers, disposal, portability, secondary use, biometrics, minors, model deployment, policy changes). Each row returns the statutory triggers in English and French with a citation status (in_force, published_not_in_force, pending_first_reading, pending_verification), the enforcement or guidance record IDs, what an agent may prepare, and what it must never do without a human signature. Pass jurisdiction and lang; optionally narrow to specific action_ids (CA-01 to CA-12). Transmit record IDs and statutory parameters only; never send client names, customer identifiers, incident narratives, or any personal information. Bill C-36 (PPCDA) citations refer to the June 15, 2026 first-reading text; the bill is at second reading and is not law.

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": {
      "jurisdiction": "<jurisdiction>",
      "lang": "<lang>"
    },
    "name": "canadian_privacy_consequential_action_lookup_v1"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesResponse language for the flat citation and note fields; rows always carry both languages.
action_idsNoNarrow to specific action IDs, CA-01 to CA-12. Omit to list every action relevant to the jurisdiction.
jurisdictionYesJurisdiction scoping the lookup.

Output Schema

NameRequiredDescriptionDefault
langYesThe language requested.
rowsYesMatching consequential actions in deterministic CA-01..CA-12 order.
row_countYesNumber of rows returned.
jurisdictionYesThe jurisdiction requested.
corpus_versionYesSemantic version of the movahedi.ca statutory corpus this answer was drawn from, for example v2026.12.0. Pin it when citing; when it changes, re-read the affected resources and the change log at https://movahedi.ca/changelog/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / rows / items / properties / statutory_provisions / items / properties / status / description
      Previous value: -"in_force: law today. pending_first_reading: Bill C-36 first-reading text, not law. pending_verification: primary-source check still open."New value: +"in_force: in effect today. published_not_in_force: final guidance published, effective May 1, 2027. pending_first_reading: Bill C-36 first-reading text, not law. pending_verification: primary-source check still open."
    • changedOutput schema / properties / rows / items / properties / statutory_provisions / items / properties / status / enum
      Previous value: -[
      -  "in_force",
      -  "pending_first_reading",
      -  "pending_verification"
      -]New value: +[
      +  "in_force",
      +  "published_not_in_force",
      +  "pending_first_reading",
      +  "pending_verification"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, and the description adds real context beyond them: corpus version v2026.12.1, the four citation status values, and the Bill C-36 first-reading caveat. It does not discuss pagination or result-size behavior, so with annotations in place a 3 is fair.

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?

Purpose is front-loaded and every clause carries substance (topics, statuses, payload limits, legal caveat). The single dense paragraph with a long inline enumeration is harder to scan than it needs to be, costing a point.

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 versioned, jurisdiction-scoped read tool this covers what an agent needs: corpus version, what a row contains, legal-status caveat for the pending bill, and a data-minimization rule. An output schema already exists, so return values need not be described further.

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 coverage is 100%, so the baseline is 3; the description goes further by mapping action_ids (CA-01 to CA-12) onto the twelve named action topics and clarifying that lang only affects flat citation/note fields while rows always carry both languages.

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 and resource ('Look up the twelve consequential actions in the Canadian privacy corpus v2026.12.1') and enumerates the twelve topics, so an agent can tell this apart from siblings like privacy_search_enforcement_actions or canadian_privacy_breach_deadline_calculator_v1 without opening a schema.

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?

Gives explicit invocation guidance ('Pass jurisdiction and lang; optionally narrow to specific action_ids') plus hard constraints on what data may be transmitted and what requires a human signature. It does not explicitly name when a sibling tool should be chosen instead, which keeps it short of a 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