Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api solutions destroy

ciso_assistant_api_solutions_destroy
DestructiveIdempotent

Delete a specified solution by ID in CISO Assistant, requiring explicit confirmation to authorize this destructive operation when the client cannot prompt.

Instructions

API endpoint that allows solutions 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_solutions_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
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description says the endpoint allows solutions to be "viewed or edited" – a read-and-mutate framing for a DELETE operation, and it never mentions deletion, irreversibility, cascade effects, or required permissions. It also ignores the `confirm` safety parameter entirely, so the only behavioral signal an agent gets comes from the annotations the description undercuts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded and free of padding, so structurally it is fine. The brevity is wasted because the single sentence carries no accurate information about the operation.

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 delete of a solution record with no output schema and only 50% parameter documentation, the description supplies none of the missing context: what is removed, whether related objects are affected, or how to confirm. An agent could not invoke this safely based on the description alone.

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 description coverage is 50% (only `confirm` is documented; `id` has no description). The description adds no meaning to either parameter – it does not say `id` identifies the solution to delete or when `confirm` must be supplied – 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 reads "API endpoint that allows solutions to be viewed or edited," which restates a generic DRF docstring and never states that this endpoint deletes a solution. Only the tool name's "destroy" suffix reveals the actual verb, and the phrase "viewed or edited" actively misdirects an agent away from the destructive purpose.

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 prerequisites, and no reference to alternatives. With well over a hundred sibling `*_destroy` tools plus `ciso_assistant_api_solutions_list`, `_retrieve`, `_update`, and `_partial_update`, the description gives an agent nothing to decide between them.

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