Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy data breaches destroy

ciso_assistant_api_privacy_data_breaches_destroy
DestructiveIdempotent

Deletes a privacy data breach record via the CISO Assistant API and requires explicit confirmation to proceed with the destructive operation.

Instructions

API endpoint that allows data breaches 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_breaches_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 declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, but the description says the endpoint lets breaches be 'viewed or edited' and never mentions permanent deletion. It adds no context beyond annotations: no irreversibility warning, no permissions note, no cascade/impact information. This is an annotation contradiction, not just an omission.

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, so it is not bloated, but nearly every word is either boilerplate or incorrect. Brevity here comes from under-specification rather than discipline, and the one clause present is front-loaded with the wrong verb.

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, open-world tool with a required id and a confirmation flag, the description supplies none of the information an agent needs before calling it: what is deleted, whether it is recoverable, and when confirmation is required. With no output schema and contradictory prose, an agent would be guessing.

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 as the confirmation gate for a destructive operation, but 'id' carries no description at all. The prose adds nothing about either parameter, not even that id identifies the breach record to be removed, 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 sentence names the resource (data breaches) but describes the operation as 'viewed or edited', which is a generic Django-REST-Framework docstring rather than the actual verb. The tool name and annotations say the operation is a destroy/delete, so the stated purpose is not just vague but wrong about what happens. Nothing distinguishes it from the sibling list/retrieve/update tools for 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 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 preconditions, and no mention of the many alternatives (privacy_data_breaches_list, _retrieve, _partial_update, _update). Worse, 'viewed or edited' actively steers an agent toward read/edit usage for a destructive endpoint, which is misleading rather than merely absent.

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