Movahedi Privacy API

Get enforcement case details

privacy_get_enforcement_case

Read-onlyIdempotent

Get the full record of one privacy enforcement action by its ID, including the plain-language summary, outcome, penalty amount, and the official regulator source link. Use this after privacy_search_enforcement_actions when you need complete details on a specific case, or when a case ID (like 'cai-2026-05-06-openai') is already known. Use when: Use when someone has a case id and wants that one case in full. Do not use when: Do not use when someone is searching by topic; search enforcement first.

Input Schema

Name	Required	Description	Default
`id`	Yes	The case ID from a search result.

Output Schema

Name	Required	Description	Default
`case`	Yes
`corpus_version`	Yes	Semantic 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.

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / corpus_version

Added value: +{
+  "description": "Semantic 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/.",
+  "examples": [
+    "v2026.12.0"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "case"
-]New value: +[
+  "case",
+  "corpus_version"
+]

First observedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context beyond that: the tool returns a complete single record including penalty and the official regulator source link, and expects an ID obtained from a prior search. No auth or rate-limit notes, but none are needed at this level.

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?

Front-loaded with the core action and return payload, then the routing rules. The 'Use when' line mildly repeats the preceding sentence about case IDs, but overall it is tight and readable.

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 single-parameter lookup with full schema coverage, annotations, and an output schema, the description covers everything an agent needs: the action, the expected ID provenance, the workflow position after search, and the shape of the result. No material gaps.

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 coverage is 100% with a regex pattern and an example ID, and the schema field text already says the ID comes from a search result. The description's mention of the ID and a sample value ('cai-2026-05-06-openai') largely restates that, so it adds little meaning beyond the schema — the baseline 3 applies.

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 ('Get the full record of one privacy enforcement action by its ID') and enumerates the payload fields (summary, outcome, penalty amount, source link). It is clearly distinguished from privacy_search_enforcement_actions, which returns many cases rather than one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit 'Use when' condition (a case ID is known and one full case is wanted) and an explicit 'Do not use when' condition (searching by topic), naming the sibling tool to use instead. Routing is unambiguous.

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

All Movahedi Privacy API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?