Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy right requests destroy

ciso_assistant_api_privacy_right_requests_destroy
DestructiveIdempotent

Deletes a privacy right request by ID in CISO Assistant, with explicit confirmation support for destructive API operations.

Instructions

API endpoint that allows right requests 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_right_requests_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.7/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 frames the endpoint as viewing/editing, which is the opposite behavioral profile. It says nothing about permanence, cascade effects, required permissions, or the confirm flag's role in destructive confirmation.

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

Conciseness3/5

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

It is a single short sentence with no padding, so it is concise, but the content is boilerplate rather than informative, and the actual action is not front-loaded or stated anywhere.

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

Completeness2/5

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

This is a destructive single-object delete with no output schema and no annotations covering permissions or side effects. The description should at minimum state what is deleted and that the action is irreversible, and it omits both.

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?

With two parameters at 50% schema coverage, the description must compensate for the undocumented id parameter, but it adds no meaning at all. It also does not explain that confirm exists to gate this irreversible deletion, leaving the confirm semantics entirely to the schema.

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 is generic DRF boilerplate: 'allows right requests to be viewed or edited.' It names the resource but gives a vague, plural verb set and never states that this endpoint deletes a single right request, which is what the tool name ('destroy') and id parameter imply.

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 and no mention of alternatives such as the sibling update/partial_update or list/retrieve tools. Worse, telling an agent the endpoint is for 'viewing or editing' actively points it toward the wrong operation.

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