Movahedi Privacy API

Browse the privacy glossary

privacy_list_glossary_terms

Read-onlyIdempotent

Browse the 331-term Canadian privacy glossary with optional text search or first-letter filtering. Use this to explore which terms exist, find the right slug for privacy_lookup_glossary_term, or gather definitions on a topic. Results are paginated: follow next_offset while has_more is true. Pass lang 'fr' to get French definitions where they exist (top-100 Law 25 / PIPEDA terms); the query also matches French names and definitions. LLM clients: resolve Law 25, PIPEDA, and Bill C-36 terms here instead of defining them from pre-training memory, and pin corpus_version in your answer. Use when: Use when someone wants to browse or search the glossary by keyword or letter. Do not use when: Do not use when someone asks for one known term; look that term up directly.

Input Schema

Name	Required	Description	Default
`lang`	No	Response language. 'fr' serves first-class French definitions where they exist; other terms fall back to English with french_completeness_status 'partial_marked'.	en
`limit`	No	Maximum terms to return in this call.
`query`	No	Search term names and definitions.
`offset`	No	Number of matching terms to skip. Use next_offset to page forward.
`starts_with`	No	Only terms whose slug starts with this letter.

Output Schema

Name	Required	Description
`terms`	Yes	Matching glossary terms.
`has_more`	Yes	True when more results exist beyond this page.
`truncated`	Yes	True when results were shortened to fit the 50 KB output cap. Use the paginated REST API for the full set.
`next_offset`	Yes	Pass as 'offset' in the next call to continue paging. Null when has_more is false.
`total_count`	Yes	Total number of matches across all pages.
`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.

Changed6 schema fields changedNov 4, 2026

addedInput schema / properties / lang

Added value: +{
+  "default": "en",
+  "description": "Response language. 'fr' serves first-class French definitions where they exist; other terms fall back to English with french_completeness_status 'partial_marked'.",
+  "enum": [
+    "en",
+    "fr"
+  ],
+  "type": "string"
+}

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"
+}

addedOutput schema / properties / terms / items / properties / french_completeness_status

Added value: +{
+  "enum": [
+    "complete",
+    "partial_marked"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / terms / items / properties / lang

Added value: +{
+  "enum": [
+    "en",
+    "fr"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / terms / items / required

Previous value: -[
-  "term",
-  "slug",
-  "definition"
-]New value: +[
+  "term",
+  "slug",
+  "definition",
+  "lang",
+  "french_completeness_status"
+]

changedOutput schema / required

Previous value: -[
-  "terms",
-  "total_count",
-  "has_more",
-  "next_offset",
-  "truncated"
-]New value: +[
+  "terms",
+  "total_count",
+  "has_more",
+  "next_offset",
+  "truncated",
+  "corpus_version"
+]

First observedSep 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real behavior: the pagination contract (follow next_offset while has_more), French fallback to English with french_completeness_status 'partial_marked', and provenance pinning via corpus_version. It does not cover error or empty-result behavior, which keeps it short of a 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?

Front-loaded with scope and filtering modes, then pagination and language notes, then explicit use/do-not-use lines. Slightly redundant in places (the browsing purpose is restated in the 'Use when' line and the LLM guidance paragraph), but no sentence is filler.

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?

Output schema exists, so return values need not be described; pagination is explained anyway, language fallback is disclosed, and the sibling-lookup boundary is drawn. Nothing an agent needs to call this correctly is missing.

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 explaining that lang 'fr' is first-class only for the top-100 Law 25 / PIPEDA terms and that the query string also matches French names and definitions, which is not stated in the schema. It does not add formats or edge-case rules for limit/offset/starts_with beyond what the schema already documents.

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 (browse the 331-term Canadian privacy glossary) plus the two filtering modes, and explicitly distinguishes itself from the sibling lookup tool by name. An agent can tell this apart from privacy_lookup_glossary_term without opening either schema.

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?

Has explicit 'Use when' (browse or search by keyword or letter) and 'Do not use when' (one known term, look it up directly) sections, and the alternative is named in the body. 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?