Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api chat documents destroy

ciso_assistant_api_chat_documents_destroy
DestructiveIdempotent

Deletes an indexed document by ID from CISO Assistant. Set the confirm flag when the client cannot answer a destructive-operation confirmation prompt.

Instructions

ViewSet for managing indexed documents.

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_chat_documents_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

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing on top of that: it does not say the document is permanently removed, what happens to its embeddings or references, or whether permissions are required. With annotations carrying the burden, the low bar is not met at all.

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 concise and front-loaded. However, brevity here comes from being generic boilerplate rather than from disciplined editing, so it earns no more than a middling score.

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?

This is an irreversible delete operation with no output schema and no annotations beyond the hint flags, so the description should carry real weight. Instead it says nothing about consequences, prerequisites, or return behavior, leaving the agent to infer everything from the tool name and the 'confirm' parameter.

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 has no description and the 'confirm' parameter's own schema text explains the confirmation handshake. The description does not clarify that 'id' is the indexed chat document identifier or what 'confirm' guards against, 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 as framework boilerplate ('ViewSet for managing indexed documents') rather than a statement of what the tool does. It names the resource loosely (indexed chat documents) but uses the vague verb 'managing' and never indicates that this tool deletes a document, which is what the name and annotations declare. It also gives no way to distinguish it from the many sibling chat_documents tools (list, retrieve, update, batch_action).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 when not to use it, and no pointer to alternatives such as partial_update or the batch action for bulk removal. The only usage signal an agent gets comes from the tool name and the destructiveHint annotation, not from the description.

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