Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy data subjects destroy

ciso_assistant_api_privacy_data_subjects_destroy
DestructiveIdempotent

Delete a privacy data subject by ID, with explicit confirmation needed only when the client cannot answer a confirmation prompt.

Instructions

API endpoint that allows data subjects to be viewed or edited.

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_data_subjects_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.5/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description claims the endpoint lets records be 'viewed or edited,' which directly contradicts the destructive semantics. It adds no context about permanence, cascading effects, or the confirm parameter's confirmation protocol.

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, so there is no verbosity problem, but that one sentence is generic Django-REST boilerplate that conveys nothing specific about this endpoint. Brevity here reflects under-specification, not efficiency.

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?

This is an irreversible deletion tool with no output schema and only partial parameter documentation, so the description carries the full explanatory burden and fails completely. An agent reading only the description could not infer that calling it destroys a data subject record.

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

Parameters2/5

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

Schema coverage is 50%: 'confirm' has a description but 'id' does not, and the description supplies no parameter meaning at all. An agent gets no hint that the id is the target data subject to be deleted.

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

Purpose2/5

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

The description reads 'API endpoint that allows data subjects to be viewed or edited,' which describes read/update behavior, not deletion. Only the tool name ('destroy') reveals the actual operation, so the description misstates the verb rather than clarifying it, and it offers no differentiation from the many sibling *_destroy endpoints.

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, no prerequisites, and no mention of alternatives such as the sibling partial_update or batch_action tools. Worse, the implied guidance ('viewed or edited') points an agent toward the wrong operation entirely.

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