Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api chat sessions destroy

ciso_assistant_api_chat_sessions_destroy
DestructiveIdempotent

Delete a chat session by ID in CISO Assistant. Use the optional confirm flag to explicitly authorize this destructive action when a client cannot answer a confirmation prompt.

Instructions

ViewSet for chat sessions with streaming message endpoint.

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_sessions_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 and openWorldHint=true, so the safety profile is covered. However, for a destructive operation the description adds nothing: no mention of what is removed (messages, attached documents), whether deletion cascades, whether it is soft or hard, or what the confirm flag guards against. The streaming-endpoint sentence actively misdirects attention away from deletion.

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 bloated. But the one sentence it spends is boilerplate about a ViewSet and an unrelated streaming endpoint, so brevity comes at the cost of any useful content.

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, open-world delete with no output schema, the description should at minimum confirm that the operation deletes the identified chat session permanently and what happens on success. It supplies none of that, leaving the annotations to carry essentially all the load.

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%: the 'confirm' parameter is documented in the schema, but 'id' has no description. The tool description adds no meaning to either parameter — it does not explain that 'id' identifies the chat session to delete or that 'confirm' must be set when the client cannot answer a prompt.

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 names the resource (chat sessions) but never states the operation. It describes a 'ViewSet ... with streaming message endpoint', which points at read/stream behavior rather than deletion, so an agent must infer the destructive purpose from the tool name and annotations alone.

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, when-not-to-use, or alternative guidance. Given the many sibling *_destroy tools in the same namespace, the description provides no help in distinguishing deleting a chat session from, say, chat_documents_destroy or chat_sessions_update.

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