Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api folders destroy

ciso_assistant_api_folders_destroy
DestructiveIdempotent

Permanently delete a CISO Assistant folder by ID, using the confirmation flag when a client cannot handle the destructive-action prompt.

Instructions

API endpoint that allows folders 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_folders_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.9/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 openWorldHint=true, and the description adds nothing to them — it never mentions deletion, cascading effects, irreversibility, or typical error conditions. Worse, 'viewed or edited' actively understates the operation, so an agent reading the prose alone would not anticipate data loss.

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?

It is a single short sentence with no padding, so it is not verbose, but the brevity comes at the cost of accuracy and usefulness. The one sentence that is present is boilerplate that does not earn its place.

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 delete with one undocumented path parameter and no output schema, the description should state that the folder record is permanently removed and what the `confirm` flag interacts with. Instead it provides only a generic DRF-style endpoint blurb, leaving the agent to reconstruct behavior from annotations and the tool name.

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 only 50%: the required `id` parameter is undocumented in the schema, and the description does not explain what kind of identifier it expects (UUID, slug, numeric ref) or where to obtain it. The `confirm` parameter is well documented in the schema, but the description contributes no meaning beyond it.

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 says only that this is an 'API endpoint that allows folders to be viewed or edited', which misstates the operation entirely: the tool name and annotations both indicate a destructive delete. The resource ('folders') is named, but the stated verb is generic boilerplate that does not distinguish this from folders_list, folders_retrieve, or folders_update among the 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 when-to-use guidance at all: nothing about when deletion is appropriate, what prerequisites or permissions are required, or what alternatives exist (e.g., partial_update). An agent has only the tool name and the destructiveHint to infer that this permanently removes a record.

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