Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api validation flows destroy

ciso_assistant_api_validation_flows_destroy
DestructiveIdempotent

Delete a validation flow by ID to remove an obsolete approval/validation process; set confirm only when the client cannot answer a confirmation prompt.

Instructions

API endpoint that allows validation flows 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_validation_flows_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.5/5.0
Behavior1/5

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

Annotations declare destructiveHint=true, idempotentHint=true and openWorldHint=true, yet the description describes the endpoint as allowing records to be 'viewed or edited' — the opposite of the irreversible removal it performs. No mention of permanent data loss, cascading effects on linked models, or that the confirm flag exists to gate the operation.

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?

A single short sentence with no padding, so it is technically concise, but its brevity is under-specification rather than efficiency — the one sentence that exists conveys incorrect and unhelpful information.

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, open-world, idempotent delete endpoint with a partially documented schema and no output schema, the description supplies none of the information an agent needs: what gets removed, whether the deletion cascades, or how the confirm parameter interacts with the operation.

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 flag is documented in the schema, but the required id parameter has no description. The tool description adds nothing — no explanation that id identifies the validation flow to delete and that confirm must be set when no interactive prompt is possible, which is exactly the gap the description should fill.

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 reads as generic Django REST framework boilerplate: 'API endpoint that allows validation flows to be viewed or edited.' The tool name and annotations indicate a destroy/delete operation, but the description names neither deletion nor the resource being removed in a way that distinguishes it from the many sibling validation-flow tools (list, retrieve, update, partial_update).

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?

No when-to-use guidance at all. With well over a hundred sibling tools including list/retrieve/update variants on the same validation_flows resource, an agent gets no signal that this is the removal path rather than the read or edit path, and no prerequisites or warnings are stated.

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