Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api document revisions destroy

ciso_assistant_api_document_revisions_destroy
DestructiveIdempotent

Permanently delete a document revision by ID, with an optional confirmation flag for clients that cannot handle prompts.

Instructions

API endpoint that allows document revisions 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_document_revisions_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.3/5.0
Behavior1/5

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

Annotations declare destructiveHint=true with readOnlyHint=false, but the description frames the endpoint as a view/edit API, effectively contradicting the declared destructive behavior. It omits permanence, cascade effects, and any prerequisites; only the schema's `confirm` parameter hints at destructiveness.

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?

It is a single short sentence, so there is no bloat, but brevity here buys nothing: the sentence is generic and inaccurate rather than front-loading the destructive semantics an agent needs.

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 delete operation with no output schema, the description must carry the behavioral burden. Instead it is absent on impact, reversibility, and permissions, and its stated purpose conflicts with the tool's actual effect.

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%: `confirm` is already documented in the schema and `id` is self-evident. The description adds no meaning to either parameter and, given low coverage, should have explained the target identifier and confirmation behavior.

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 says the endpoint "allows document revisions to be viewed or edited," which is misleading: the tool name ends in `destroy` and the annotations declare destructiveHint=true. It does not state that a revision is deleted, and it fails to distinguish this tool from the many document-revision siblings (retrieve, update, list, etc.).

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 and no mention of alternatives such as the retrieve/update siblings. Worse, the implied usage ("viewed or edited") actively steers an agent toward the wrong operation for a delete endpoint.

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