Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api entity assessments destroy

ciso_assistant_api_entity_assessments_destroy
DestructiveIdempotent

Delete a specific entity assessment by ID to remove it from the GRC system; confirm the destructive action when prompted.

Instructions

API endpoint that allows entity 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_entity_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.1/5.0
Behavior1/5

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

Annotations declare destructiveHint=true while the description frames the endpoint as view/edit, so the description actively contradicts the safety-critical structured signal. It discloses nothing about irreversibility, permission requirements, or side effects of cascading deletion.

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?

The single sentence is short but that brevity reflects under-specification rather than economy of expression. It is generic DRF boilerplate that wastes the one line available on content that does not describe the tool.

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, potentially cascading delete with no output schema and an undocumented required identifier, the definition provides none of the context an agent needs before invoking it. Nothing warns of data loss or points to inspection tools like entity_assessments_retrieve or cascade_info_retrieve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% — 'id' is undocumented and the destructive 'confirm' flag is described only in the schema itself. The description adds no meaning to either parameter and does not explain what 'id' refers to in the entity-assessment hierarchy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says the endpoint 'allows entity assessments to be viewed or edited', which does not describe the tool's actual operation at all. The name and annotations indicate a permanent delete of a single entity assessment, so the stated purpose is not merely vague but misleading.

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, no warning that this is a hard delete, and no mention of siblings such as entity_assessments_batch_action_create, partial_update, or cascade_info_retrieve that would help an agent choose correctly. The required 'confirm' parameter and when to set it are never discussed.

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