Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api vulnerabilities destroy

ciso_assistant_api_vulnerabilities_destroy
DestructiveIdempotent

Deletes a vulnerability by ID from CISO Assistant and accepts a confirm flag for clients that cannot answer the destructive-action prompt.

Instructions

API endpoint that allows vulnerabilities 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_vulnerabilities_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.8/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 carried structurally; the description adds nothing. It arguably misdescribes the operation as viewing/editing, and says nothing about irreversibility, cascade effects, or when the schema's 'confirm' flag is required.

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?

A single short sentence, so there is no bloat, but the sentence is boilerplate that conveys no useful information about this specific endpoint; brevity here reflects an auto-generated template rather than deliberate concision.

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, irreversible operation with no output schema and only 50% parameter coverage, the definition should explain what is deleted and what the confirm flag does. The description leaves the agent with no more information than the tool name and annotations provide.

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%, so the description is expected to compensate, but it mentions neither the required 'id' nor the 'confirm' flag. The confirm parameter's meaning comes entirely from its inline schema description, not from the tool description.

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 the endpoint 'allows vulnerabilities to be viewed or edited', which is generic CRUD boilerplate and omits the one thing the tool actually does: delete a vulnerability (the name's 'destroy' and the destructiveHint). It neither states a specific verb matching the operation nor distinguishes this tool from the many sibling _destroy endpoints in the list.

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, and what is present ('viewed or edited') actively steers toward read/update usage for what is a delete operation. No mention of alternatives such as ciso_assistant_api_vulnerabilities_partial_update or _retrieve when deletion is not actually intended.

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