Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api evidence revisions destroy

ciso_assistant_api_evidence_revisions_destroy
DestructiveIdempotent

Deletes an evidence revision in CISO Assistant, requiring explicit confirmation when the client cannot prompt, to prevent accidental removal.

Instructions

API endpoint that allows evidence 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_evidence_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.7/5.0
Behavior1/5

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

The annotations declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, but the description describes a benign view/edit endpoint and says nothing about permanent deletion, irreversibility, or the confirmation requirement. That directly conflicts with the declared destructive behavior. The 'confirm' parameter's role as a safety gate for an irreversible deletion is left entirely unexplained.

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 comes from boilerplate rather than from precision. The one sentence that exists is inaccurate, so it fails to earn its place.

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 an irreversible delete operation with a required id and an optional confirm flag, plus no output schema, the description leaves every decision-relevant fact unstated: what is destroyed, whether it can be undone, what permissions it needs, and what a successful response looks like. An agent cannot safely call this tool on the strength of 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 only 50%: the 'confirm' parameter is documented in the schema, but the required 'id' has no description at all. The description adds no meaning to either parameter and does not explain what the id identifies or why confirmation may be needed. With low coverage, the description should compensate, and it does not.

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 is generic DRF boilerplate: 'API endpoint that allows evidence revisions to be viewed or edited.' It never states that this tool deletes an evidence revision, so the stated purpose actually points away from what the operation does. Only the tool name's 'destroy' suffix lets an agent infer the real action, and it does nothing to distinguish this from the many sibling evidence-revision tools.

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 or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives such as ciso_assistant_api_evidence_revisions_partial_update or _retrieve. Worse, saying the endpoint is for 'viewing or editing' would steer an agent toward using it for reads or updates. The only usable signal is the tool name.

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