Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api entities destroy

ciso_assistant_api_entities_destroy
DestructiveIdempotent

Deletes a CISO Assistant entity by ID and returns a 409 Conflict with protected dependencies when deletion is blocked; supports explicit confirmation.

Instructions

Convert Django's ProtectedError into a 409 Conflict with the list of

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_entities_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.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description does add one genuinely useful behavioral fact — that deletion may be blocked by protected relations and surface as a 409 Conflict with a list of dependents — but the sentence is truncated, so the agent cannot tell what the list contains or how to recover.

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 but broken rather than concise: a single trailing fragment with no verb describing the operation and no complete clause. Brevity here reflects truncation, not disciplined editing, and the only substantive content is buried in an error-handling aside.

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 single-record delete with no output schema, the description should at minimum state the target resource, the effect, and what a blocked deletion looks like. Only the last of these is partially present, and the cascade/confirmation semantics an agent needs before calling a destructive endpoint are absent.

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%: 'confirm' is documented in the schema, but 'id' has no description at all. The description adds nothing about either parameter — not what id identifies, not when confirm is required beyond the schema's own note. With a coverage gap, the description was expected to compensate and does not.

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 never says what the tool does. It is an implementation note about converting Django's ProtectedError into a 409 Conflict, ending mid-sentence at 'with the list of'. Nothing states that this deletes an entity identified by id, so the agent must infer the purpose entirely from the tool name and the destructiveHint annotation.

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 alternatives such as ciso_assistant_api_entities_partial_update or cascade_info_retrieve, and no prerequisites such as required permissions. The text provides zero routing information among the many sibling destroy and update tools.

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