Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api chat questionnaire questions destroy

ciso_assistant_api_chat_questionnaire_questions_destroy
DestructiveIdempotent

Delete a questionnaire question by ID in CISO Assistant; set confirm to authorize this destructive operation when prompted.

Instructions

api_chat_questionnaire_questions_destroy

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_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

C2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description, however, repeats none of that context in prose and says nothing about whether deletion is permanent, what happens to linked questionnaire runs or answers, or what confirmation semantics apply beyond the schema's confirm flag.

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?

The string is trivially short with no wasted words, but it is under-specification rather than conciseness: it is a single snake_case identifier that conveys no front-loaded information an agent could not already read from the tool name.

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 mutation with no output schema, the definition should at minimum state that it permanently removes a questionnaire question and clarify the confirm flag's role. Annotations carry the destructiveness signal, but the description leaves the operational picture (permanence, referential impact, when confirmation is required) essentially blank.

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%: the confirm parameter is well documented in the schema, but id has no description and the tool description supplies no compensating explanation of what identifier is expected (question UUID, run-scoped id, etc.). With coverage below the 80% baseline, the description was responsible for filling the gap 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 is literally the tool name re-serialized ("api_chat_questionnaire_questions_destroy"), so it restates the identifier rather than explaining what the tool does. An agent can infer deletion of a chat questionnaire question from the name alone, but the description contributes no verb-plus-resource statement of its own and does nothing to distinguish it from siblings such as chat_questionnaire_runs_destroy or chat_documents_destroy.

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 prerequisites, and no mention of alternatives. The only implied usage is the one carried by the word "destroy" in the tool name; the description text itself adds nothing about which questionnaire-question scenarios should invoke this versus cascade_info or retrieve tools.

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