Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api chat questionnaire runs destroy

ciso_assistant_api_chat_questionnaire_runs_destroy
DestructiveIdempotent

Deletes an experimental questionnaire prefill run by ID and requires confirmation for this destructive operation.

Instructions

Experimental: questionnaire prefill runs.

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_chat_questionnaire_runs_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 readOnlyHint=false, so the safety profile is technically covered by structured data. The description contributes only the 'Experimental' warning and is silent on what gets removed (the run and its extracted questions/mappings?), whether parent sessions are affected, and whether the operation is recoverable. For a permanent delete of an AI-generated dataset, that is a meaningful gap, though no contradiction with annotations exists.

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?

Only a single fragment, so nothing is wasted, but this is under-specification rather than conciseness. There is no front-loaded statement of the destructive action or of the target object, which is the one thing an agent most needs before calling it.

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?

A permanently destructive, open-world delete tool with an undocumented id parameter and no output schema demands at least a sentence on what is deleted and any cascade effects. The description supplies neither, so an agent has no basis to judge consequences before invoking it.

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 50%: only 'confirm' is documented, and its text already explains the client-cannot-prompt case. The description adds nothing about what 'id' identifies (a questionnaire run vs a session vs a question) or how the confirm flag interacts with destructiveHint. With half the parameters undocumented in the schema, the description was expected to compensate and does not.

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 'Experimental: questionnaire prefill runs' names only a resource fragment and never states the action. The verb 'destroy' exists solely in the tool name/title, so the agent must infer that this deletes a questionnaire prefill run rather than reading it. It also does not distinguish this from siblings like ciso_assistant_api_chat_questionnaire_runs_batch_action_create or _update.

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?

No when-to-use, when-not-to-use, or alternative routing is given. The word 'Experimental' implies caution but the description never says to prefer a softer sibling (partial_update, batch_action) or under what conditions deletion is appropriate. The agent gets no eligibility criteria at all.

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