Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api risk assessments destroy

ciso_assistant_api_risk_assessments_destroy
DestructiveIdempotent

Delete a risk assessment by ID, with optional confirmation to prevent accidental data loss.

Instructions

API endpoint that allows risk assessments 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_risk_assessments_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, readOnlyHint=false, idempotentHint=true and openWorldHint=true, so the destructive nature is already known. The description not only fails to add context (irreversibility, cascading effects on linked action plans/scenarios, required permissions), it actively implies viewing/editing, contradicting the destructive annotation.

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 it is not bloated, but the sentence is pure boilerplate that conveys no actionable information and would have been better replaced by even one accurate clause about deletion.

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, single-parameter delete endpoint with no output schema, the description should say what is removed and what happens to dependent records. Instead it is silent on all of that and mischaracterizes the operation, leaving the agent unable to invoke it safely.

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 50%: the 'confirm' flag is documented in the schema with its purpose, but 'id' has no description. The description contributes nothing about identifier format, whether the id is a UUID or reference, or when confirm must be set, so it fails to compensate for the uncovered parameter.

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 risk assessments to be viewed or edited', which restates generic Django REST framework boilerplate rather than the actual action. The tool name and annotations show this is a destroy/delete operation, but the stated purpose points at viewing/editing, so an agent cannot confidently tell what the tool does from the description alone.

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 on when to use this tool versus the many siblings such as risk_assessments_update, risk_assessments_partial_update, or risk_assessments_batch_action_create. Worse, the wording steers the agent toward non-destructive usage with no warning about deletion.

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