Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy processing natures destroy

ciso_assistant_api_privacy_processing_natures_destroy
DestructiveIdempotent

Permanently deletes a privacy processing nature by ID from CISO Assistant. Use it to remove obsolete processing nature records from your GRC compliance data.

Instructions

api_privacy_processing_natures_destroy

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_processing_natures_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 already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally, but the description adds nothing beyond that: it does not say what is irreversibly removed, whether related processings/purposes are affected by the deletion, or whether permissions are required. For an irreversible operation with zero descriptive text, there is no supplementary behavioral context at all.

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?

The description is extremely short, but this is under-specification rather than conciseness: a single snake_case token is not a sentence, has no front-loaded explanation, and gives the agent nothing to structure its decision around. There is no wasted wording because there is essentially no wording.

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 a destructive, open-world mutation with no output schema and a cascade-sensitive domain object (privacy processing natures are referenced by processings), yet the description does not cover return behavior, cascade effects, error conditions, or the confirmation flow. Against this complexity level, the definition is completely inadequate.

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 description coverage is 50%: the 'confirm' parameter is documented in the schema itself, while 'id' is undocumented but self-evidently the target identifier. The description contributes nothing to clarify whether 'id' is a slug, UUID, or integer, nor how 'confirm' interacts with the server-side confirmation prompt beyond what the schema already states.

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 literally the tool name string 'api_privacy_processing_natures_destroy' with no verb, no sentence, and no explanation of what a 'processing nature' is or what destroying one entails. Only the 'destroy' token conveys any meaning, and that is already in the name and annotations. This is a tautology rather than a statement of purpose.

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 guidance on when to use this tool, no prerequisites, and no mention of the sibling tools (natures_list, natures_retrieve, natures_update) that an agent should consider first. An agent must infer entirely from the name that this is the deletion counterpart in the privacy processing natures CRUD family.

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