Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api role assignments destroy

ciso_assistant_api_role_assignments_destroy
DestructiveIdempotent

Deletes a role assignment by its ID, with an optional confirmation flag for destructive operations when client prompts are unavailable.

Instructions

API endpoint that allows role assignments 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_role_assignments_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.7/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 frames the endpoint as allowing records to be 'viewed or edited', which frames it as non-destructive read/update. It also says nothing about what deletion implies (assignment removal, permission loss, cascading effects), though the schema does at least document the 'confirm' flag.

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 one short sentence, but it is generic DRF ViewSet boilerplate that does not front-load the actual action. Brevity here reflects under-specification rather than efficiency; every word is wasted because none describes the delete.

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 an irreversible destructive operation with an undocumented id parameter and no output schema, the description must at minimum state what is destroyed and any permission or confirmation requirement. It provides none of that, and its 'viewed or edited' framing actively misleads about the tool's effect.

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%: 'id' is undocumented in the schema and the description does not clarify what identifier form is expected. The 'confirm' parameter's semantics are already fully explained in the schema, so the description adds nothing beyond structured data and fails to compensate for the uncovered 'id'.

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 names the resource (role assignments) but states the wrong operation set: 'viewed or edited'. The tool actually deletes a role assignment, as the name suffix '_destroy' and destructiveHint indicate, so the purpose an agent would infer is misleading rather than merely vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative guidance at all. Sibling destroy endpoints (e.g. ciso_assistant_api_role_assignments_update, ciso_assistant_api_role_assignments_batch_action_create) are never referenced, so an agent gets no routing help between deleting, editing, or batch actions on role assignments.

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