Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api questions destroy

ciso_assistant_api_questions_destroy
DestructiveIdempotent

Deletes a specific CISO Assistant question by ID, using a confirmation flag when a client cannot answer a destructive-action prompt.

Instructions

API endpoint for Question CRUD.

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_questions_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, idempotentHint=true, and openWorldHint=true, so the safety profile is known without the description. The description adds nothing beyond that: it does not say what related data (choices, answers) may be deleted, whether the operation is reversible, or what permissions are required.

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?

One short sentence with no bloat, but it is under-specification rather than conciseness. The single sentence carries no actionable information and is not front-loaded with the delete semantics an agent needs.

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, idempotent delete on a Question entity with no output schema, the description should at minimum say what is removed and any cascade consequences. It says none of that; only the annotations rescue the definition from being fully uninformative.

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 coverage is only 50% — the required 'id' has no description at all, and the 'confirm' escape hatch is documented only in the schema. The description contributes zero parameter meaning, leaving the single required argument (which ID namespace? question UUID?) undefined in both places.

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 restates the resource name ('Question') but pairs it with a generic 'CRUD' label instead of the delete verb the tool name promises. With siblings like questions_create, questions_retrieve, questions_update, and questions_partial_update all present, an agent gets no signal that this specific tool deletes a question.

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 guidance, no preconditions, and no reference to alternatives such as questions_partial_update or questions_cascade_info_retrieve (which would reveal dependencies before deletion). The word 'CRUD' arguably points the agent in the wrong direction by implying a multi-operation endpoint.

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