Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy data transfers destroy

ciso_assistant_api_privacy_data_transfers_destroy
DestructiveIdempotent

Deletes a privacy data transfer by ID in CISO Assistant, requiring explicit confirmation for the destructive operation.

Instructions

API endpoint that allows data transfers 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_transfers_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?

The description says the endpoint allows data transfers to be 'viewed or edited', while annotations declare readOnlyHint=false and destructiveHint=true. That is a direct contradiction on the most consequential attribute of the tool: whether it destroys data. Nothing about confirmation, irreversibility, or cascade effects is disclosed beyond the schema's confirm field.

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 single sentence is short but is the wrong sentence: brevity here comes at the cost of the only information that matters (that the operation deletes). It is under-specified rather than concise.

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, irreversible mutation with no output schema and a partially undocumented input schema, the description should state consequences and confirmation behavior. It supplies none, and instead mischaracterizes the operation, leaving an agent unable to call it safely.

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 only 50% – the required 'id' parameter carries no description, and the 'confirm' flag is documented in the schema itself rather than the description. The description adds no meaning about what 'id' identifies or when 'confirm' must be set to true, so it fails to compensate for the coverage gap.

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 names the resource (data transfers) but states the wrong operations: 'viewed or edited' when the tool name, the destroy suffix, and the annotations all indicate a permanent delete. An agent reading only the description would believe this is a read/write endpoint and would not know it removes a record.

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 mention of the irreversible nature of the call, and no reference to sibling alternatives such as ciso_assistant_api_privacy_data_transfers_retrieve or _partial_update that an agent should pick for viewing or editing. The implied 'view or edit' usage actively points away from the correct destruction scenario.

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