Movahedi Privacy API

Search the privacy API operations

privacy_search_api

Read-onlyIdempotent

Search the movahedi.ca public API by plain question, without guessing an endpoint. Use this when unsure which operation fits a question, for example 'has anyone been fined for facial recognition' or 'what does PIPEDA mean'. Returns matching operations with method, path, summary, parameters, use-when and do-not-use guidance, and one example REST query each, scored deterministically with no model call. Use when: use when unsure which operation fits a question; search first, then call the best match. Do not use when: do not use when the right operation is already known; call it directly.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum operations to return, default 5.
`query`	No	Plain question about privacy data, up to 120 characters.

Output Schema

Name	Required	Description
`results`	No
`data_version`	No
`corpus_version`	No	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/.
`operation_index`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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"
+}

AddedOct 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context, that results are 'scored deterministically with no model call' and that each hit carries method, path, summary, parameters, use-when/do-not-use guidance and an example query. That goes beyond the annotations, though it does not discuss result limits or empty-result behavior.

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 purpose and examples are front-loaded and the size is reasonable. There is some redundancy, since 'use when unsure which operation fits a question' is stated in the opening sentence and repeated verbatim in the 'Use when:' clause, and the phrasing 'use when: use when' reads awkwardly.

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 a two-parameter read-only discovery tool with a full schema, complete annotations and an output schema, the description covers purpose, selection criteria and result shape. The only minor gap is guidance on what an empty or low-confidence match means.

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 100%, so both parameters are already documented, and the description correctly reinforces that the input is a plain question rather than an endpoint or keyword syntax. It adds the expectation that the returned entries carry actionable detail, but says nothing additional about the limit parameter.

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 ('Search the movahedi.ca public API') plus the key qualifier 'by plain question, without guessing an endpoint,' and supports it with concrete example questions. That framing distinguishes it from the sibling lookup tools, which target a single known domain object.

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 explicit when-to-use ('use when unsure which operation fits a question; search first, then call the best match') and explicit when-not-to-use ('do not use when the right operation is already known; call it directly'). The alternative behavior is named, not merely implied.

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?