Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy purposes destroy

ciso_assistant_api_privacy_purposes_destroy
DestructiveIdempotent

Deletes a privacy purpose by ID, requiring explicit confirmation for this destructive operation.

Instructions

API endpoint that allows purposes 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_purposes_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.3/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description frames the tool as view/edit. It never mentions permanent deletion, cascade effects on processings that reference the purpose, or the `confirm` flag's role. This contradicts the annotations rather than adding context.

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, but it is generic boilerplate that carries no useful information and actively misdirects. Brevity here reflects under-specification rather than 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?

For an irreversible delete with no output schema, the description should cover what gets removed, prerequisites, and confirmation behavior. None of that is present, and the one sentence it does contain is wrong about what the tool does.

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` is documented in the schema, `id` is only typed as a string. The description adds no meaning to either parameter and never explains that `id` is the identifier of the purpose being destroyed or when to set `confirm`.

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 says the endpoint 'allows purposes to be viewed or edited,' which never states that the tool deletes a privacy purpose. The name and title say 'destroy', but the description omits the actual operation, so it is misleading rather than merely vague.

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 warning about irreversibility, and no pointer to alternatives such as `ciso_assistant_api_privacy_purposes_update` or `..._partial_update` for editing. The agent is given nothing to distinguish this from a read 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