Democruit

Change privacy consents

update_consents

DestructiveIdempotent

Change the user's privacy and communication consents. Requires conversation confirmation. Operations: consents. Returns the response envelope; nextActions list what the user can do next, primary first. Use confirm: false for a preview, then repeat identical inputs with confirm: true and the preview confirmationToken after the user confirms.

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": {
      "operation": "<operation>",
      "confirm": "<confirm>"
    },
    "name": "update_consents"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Set to true only after the user has explicitly confirmed this action in the conversation. Describe what will change to the user first.
`consents`	No	The consents supplied by the user. Follow the type and allowed values in this schema.
`operation`	Yes	Choose the task. Each operation accepts only its own fields.
`confirmationToken`	No	Token returned by the preview. Send it unchanged with confirm: true; it is valid for 15 minutes and only for the previewed inputs.

Output Schema

Name	Required	Description	Default
`data`	No
`page`	No
`error`	No
`links`	No
`status`	Yes
`notices`	No
`polling`	No
`summary`	Yes
`agentHint`	No
`nextActions`	Yes
`appliedDefaults`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

removedInput schema / allOf

Removed value: -[
-  {
-    "if": {
-      "properties": {
-        "operation": {
-          "enum": [
-            "consents"
-          ]
-        }
-      },
-      "required": [
-        "operation"
-      ]
-    },
-    "then": {
-      "required": [
-        "confirm"
-      ]
-    }
-  }
-]

addedInput schema / properties / confirmationToken

Added value: +{
+  "description": "Token returned by the preview. Send it unchanged with confirm: true; it is valid for 15 minutes and only for the previewed inputs.",
+  "maxLength": 200,
+  "type": "string"
+}

AddedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely useful context the annotations cannot: the mandatory confirmation gate, the two-step preview flow, and that the envelope carries a nextActions list ordered by priority. It stops short of saying what 'destructive' means here, e.g. whether omitted consents are cleared or left unchanged.

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?

Three front-loaded sentences with no filler: purpose, then confirmation requirement, then the preview/confirm sequence. The 'Operations: consents' fragment is close to wasted space for a single enum value, keeping it just short of top marks.

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?

An output schema exists, so return-shape explanation is not strictly required, and annotations cover the safety profile. The description is nearly complete for a four-parameter destructive mutation with nested objects, with the only real gap being the semantics of partially supplied consents.

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%, so the schema already explains confirm, consents, operation, and confirmationToken individually, which sets the baseline at 3. The description adds only the cross-call linkage between confirm and confirmationToken (repeat identical inputs), a modest increment over what each property already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (change) and resource (the user's privacy and communication consents), and the 'Operations: consents' line confirms a single-operation tool. It is clearly separable from siblings like update_account or update_item, though it never explicitly contrasts with them.

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 a concrete, ordered procedure: requires conversation confirmation, call with confirm: false for a preview, then repeat identical inputs with confirm: true plus the returned confirmationToken. That is strong when-and-how guidance, but there is no explicit when-not or reference to an alternative tool for related account changes.

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

All Democruit 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?