Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api compliance assessments destroy

ciso_assistant_api_compliance_assessments_destroy
DestructiveIdempotent

Delete a compliance assessment by ID to remove outdated or incorrect records. Set confirm to true only when the client cannot answer a confirmation prompt.

Instructions

API endpoint that allows compliance 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_compliance_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 and readOnlyHint=false, but the description describes a read/edit capability with no mention of permanent deletion, cascade effects, or any irreversibility warning. This directly contradicts the structured safety profile, so the description fails the one job that matters most here.

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 with no bloat, but brevity here comes from under-specification rather than efficiency — the one sentence conveys the wrong action entirely.

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, non-idempotent-in-effect delete operation with no output schema, the description provides no completeness at all: no warning about permanence, no note that the referenced assessment's requirements/answers go with it, and no mention of the confirm semantics.

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%: 'confirm' is documented in the schema, but 'id' has no schema description and the tool description adds nothing about what 'id' identifies (compliance assessment identifier) or that 'confirm' must be set when no confirmation prompt is available. With below-adequate coverage, the description should compensate and 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 says the endpoint 'allows compliance assessments to be viewed or edited', which restates a generic CRUD viewset docstring and never states that this tool deletes an assessment. The actual destructive purpose is only inferable from the tool name suffix 'destroy' and the annotations, not from the description itself.

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 sibling retrieve/list/update tools (e.g. ciso_assistant_api_compliance_assessments_retrieve or _partial_update). Worse, by framing the tool as 'viewed or edited' it actively points the agent toward the wrong usage.

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