Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api answers destroy

ciso_assistant_api_answers_destroy
DestructiveIdempotent

Deletes a specific CISO Assistant answer by ID, with a confirmation flag for destructive API client requests.

Instructions

API endpoint for Answer 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_answers_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.5/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the tool's safety profile is known from structured data. The description adds nothing beyond that: it does not say what is destroyed, whether related objects cascade, whether permissions are required, or what a successful response looks like. Calling a delete endpoint generic "CRUD" also mislabels the mutation rather than clarifying it.

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, so there is no wasted wording, but brevity here reflects under-specification rather than economy. The one clause present does not convey the operation, the target, or the risk.

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 deletion endpoint with no output schema, the description should at minimum state the irreversible removal of an Answer and the confirm handshake. It states none of that, leaving the agent dependent entirely on annotations and the tool name.

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%: the confirm parameter is well documented in the schema, but id carries no description, and the tool description supplies no meaning for either parameter. Nothing is added about id format (UUID, integer, ref) or about when confirm must be set to true, so the description 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.

Purpose2/5

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

The description says only "API endpoint for Answer CRUD," which restates the resource but names no specific operation. For a tool whose name is _destroy, describing it as generic CRUD actually obscures that this deletes an Answer, and it does nothing to distinguish it from the many sibling answers_* endpoints (create, list, retrieve, update, partial_update).

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 prerequisites, no mention of the sibling alternatives such as answers_update or answers_batch_action_create, and no warning about when deletion is inappropriate. An agent has to infer everything from the tool name and the destructive annotation.

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