Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api findings destroy

ciso_assistant_api_findings_destroy
DestructiveIdempotent

Deletes a CISO Assistant finding by ID, with optional confirmation for destructive operations, to remove outdated or incorrect finding records.

Instructions

api_findings_destroy

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_findings_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, openWorldHint=true and readOnlyHint=false, so the safety profile is covered by structured data and the description is not required to repeat it. However, the description adds nothing at all: it does not say the deletion is permanent, whether dependent objects cascade, or what permissions are needed. A 3 would require at least one piece of added behavioral context, and there is none.

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?

"Concise" only in the sense of being a single token; it is under-specified rather than efficient. There is no sentence to front-load and no information hierarchy, so brevity here provides no benefit.

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 single-record deletion with no output schema, an agent needs to know what gets removed, whether it is recoverable, and what to do about the confirm flag when interaction is impossible. None of that is present; only the annotations carry the irreversible/destructive signal, leaving the description functionally empty.

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 well documented in-schema, but id has no description at all, so an agent must guess whether it is the finding's UUID, a reference id, or an internal numeric key. The description contributes zero parameter meaning and therefore does not 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?

"api_findings_destroy" is a verbatim restatement of the tool name with the underscores stripped; it names no resource in human terms and gives no specificity beyond what the identifier already encodes. An agent must infer from the name alone that this deletes a single finding record identified by id.

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 guidance whatsoever on when to use this tool, when not to, or which sibling to prefer. With dozens of other *_destroy tools in the sibling list, nothing here distinguishes deleting a finding from deleting a findings_assessment or any other resource.

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