Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy processings destroy

ciso_assistant_api_privacy_processings_destroy
DestructiveIdempotent

Permanently deletes a privacy processing record by ID, with an optional confirmation flag for destructive operations.

Instructions

Generic export mixin for CSV/XLSX exports.

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": {
      "id": "<id>"
    },
    "name": "ciso_assistant_api_privacy_processings_destroy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.12
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
      +  "type": "boolean"
      +}
  2. First observedv2.3.6

TDQS

D1.1/5.0
Behavior1/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, while the description frames the operation as an export mixin, i.e. a read/retrieval behavior. It gives no information about irreversible deletion, cascade effects, or the confirmation requirement that a destructive tool needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, but brevity here reflects under-specification rather than efficiency. The one sentence present is actively misleading, so structure cannot rescue it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive single-object delete with an explicit confirmation parameter and no output schema, the description should explain what gets removed and when confirmation is needed. Instead it describes an unrelated export mixin, leaving the definition wholly inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the schema documents 'confirm' as an explicit destructive-operation confirmation, but 'id' is undocumented. The description compensates for none of this and explains neither parameter, so it adds zero meaning beyond the schema and contradicts the destructive framing the schema implies.

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

Purpose1/5

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

The description reads "Generic export mixin for CSV/XLSX exports," which has nothing to do with the tool's name and title (privacy processings destroy). It describes an export helper rather than a deletion of a privacy processing, so an agent cannot determine the tool's actual purpose from it.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all; worse, the only stated usage (CSV/XLSX export) points the agent toward the wrong sibling tools (privacy_processings_export_csv_retrieve / export_xlsx_retrieve) and away from this destructive endpoint.

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

Deploy Server

Other Tools