Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api incidents destroy

ciso_assistant_api_incidents_destroy
DestructiveIdempotent

Deletes a specified incident by ID, requiring confirmation for this destructive operation.

Instructions

Generic export mixin for CSV/XLSX exports.

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_incidents_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.1/5.0
Behavior1/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description frames the tool as an export mixin, which implies a non-destructive read. It never states that a record is permanently removed, what cascade effects occur (cf. incidents_cascade_info_retrieve), or whether the action is reversible. The description contradicts the annotated safety profile and adds nothing useful beyond it.

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 text is short and front-loaded, but its brevity comes from being an unfilled template rather than from disciplined editing. A single boilerplate sentence about an export mixin conveys no actionable information, so there is nothing here that earns its place.

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 no annotations beyond hints. An adequate definition would state what gets destroyed, whether dependent records cascade, and what the confirm flag guards against. None of that is present, and the export framing is unrelated to the operation, so the definition is wholly inadequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description needs to clarify the undocumented 'id' parameter and the deletion target, but it says nothing about parameters at all. The 'confirm' flag's confirmation semantics exist only in the schema. No value is added over structured fields, and the coverage gap is left unaddressed.

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 reads "Generic export mixin for CSV/XLSX exports" on a tool named incidents_destroy. It describes exporting data, not deleting an incident, so an agent would form the wrong idea of the tool's resource and verb. This is not merely vague — it is actively misleading and fails to distinguish the tool from the many genuine *_export_csv_retrieve siblings.

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 delete an incident, what prerequisites or permissions apply, or which sibling to use for related operations. The only implied usage — exporting — is wrong. An agent has no basis for choosing this tool over incidents_partial_update, incidents_batch_action_create, or the export/retrieve siblings.

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