Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api user groups destroy

ciso_assistant_api_user_groups_destroy
DestructiveIdempotent

Permanently delete a CISO Assistant user group by ID, using the confirm flag when a client cannot answer a destructive-operation prompt.

Instructions

API endpoint that allows user groups 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_user_groups_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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is known without the description. The description adds nothing beyond that and is misleading: it describes viewing and editing, never states that a user group will be permanently removed, and says nothing about permissions, cascading effects on members, or irreversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short and contains no filler, so it is concise. However, brevity here comes from being vague rather than from being front-loaded with the relevant destructive-operation detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive DELETE with no output schema, an agent needs to know that this permanently removes a user group and what `confirm` is for. The description supplies neither, so it is inadequate for the tool's risk level even though the parameter count is small.

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` carries its own description, but the required `id` is undocumented. The description adds no meaning to either parameter and does not explain that `id` identifies the group to be deleted or that `confirm` exists to authorize the irreversible deletion.

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 only that the endpoint "allows user groups to be viewed or edited," which restates the resource but not the operation. The tool name and title say "destroy," yet the description never mentions deletion, so an agent reading only the description would misclassify the operation.

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, when not to, or which sibling to pick (for example api_user_groups_retrieve for reading or api_user_groups_update for editing). The generic phrasing actively blurs the boundary with the read and update siblings.

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