Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api users destroy

ciso_assistant_api_users_destroy
DestructiveIdempotent

Delete a CISO Assistant user by ID through the API, using an optional confirmation flag when the client cannot answer a destructive-action prompt.

Instructions

API endpoint that allows users 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_users_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.3/5.0
Behavior1/5

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

Annotations declare a destructive, non-read-only, idempotent operation, while the description frames the endpoint as view/edit. The description adds no behavioral context of its own: nothing about permanently removing a user, cascade effects on role assignments, or permission requirements.

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, but brevity is worthless when the sentence conveys the wrong operation. The space saved is space that should have described the delete semantics.

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 tool requiring an id and an optional explicit confirmation, the description provides nothing an agent needs: no deletion semantics, no confirmation guidance, no warning that the action is irreversible.

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%: 'id' is undocumented and 'confirm' is described only in the schema itself. The description explains neither the identifier to delete nor the confirmation flag, so it fails to compensate for the coverage gap.

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 users to be viewed or edited', but the tool name ends in _destroy and the annotations declare destructiveHint=true. It names the resource but misstates the action, so an agent reading only the description would not know this deletes a user.

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 mention of the sibling operations that read or update users (api_users_retrieve, api_users_update), and no warning about prerequisites or irreversibility. The only usage-adjacent signal is the schema's 'confirm' flag, which the description never references.

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