Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy data recipients destroy

ciso_assistant_api_privacy_data_recipients_destroy
DestructiveIdempotent

Deletes a privacy data recipient by ID; set confirm to authorize deletion when the client cannot respond to a confirmation prompt.

Instructions

API endpoint that allows data recipients 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_recipients_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.8/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 endpoint as one that allows records to be 'viewed or edited.' That contradicts the declared safety profile and hides the irreversible deletion, which is the single most important behavior for this tool. This is a serious annotation contradiction.

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 under-specified rather than concise: the only content it delivers is inaccurate, so brevity provides no benefit here.

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?

For a destructive, irreversible mutation with no output schema, the description should state that deletion is permanent, that confirm is needed when no interactive prompt is available, and what happens to linked processing records. None of that is present, so an agent cannot 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 50%: the confirm parameter is documented in the schema, but id carries no description. The description adds no meaning to either parameter and never mentions that confirm exists or that id identifies the recipient to delete, 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 recipients) but the stated action, 'viewed or edited,' is wrong: this endpoint is a destroy/DELETE operation, as the tool name and destructiveHint make clear. An agent reading only the description would not know it deletes anything, and nothing distinguishes it from the sibling list/retrieve/update tools on the same resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. Given siblings such as ciso_assistant_api_privacy_data_recipients_retrieve, _partial_update, _update and _list, the description should say to use this only to permanently remove a recipient, but it says nothing about selection or prerequisites.

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