Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api task nodes destroy

ciso_assistant_api_task_nodes_destroy
DestructiveIdempotent

Deletes a task node by ID in CISO Assistant; use confirm=true when a client cannot handle the destructive-action confirmation prompt.

Instructions

api_task_nodes_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_task_nodes_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.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is disclosed structurally. The description adds nothing on top: no statement of what is destroyed (the node and its children?), whether evidence links are cascaded, or what permissions are required. It does not contradict the annotations, but it contributes no behavioral context of its own.

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 token, so there is no wasted wording, but this is under-specification rather than conciseness. There is no front-loaded statement of effect or scope for an agent to anchor on.

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?

This is a destructive, open-world delete operation with no output schema and a partially undocumented schema, so the description must carry the burden. Instead it repeats the name, leaving the agent without any information on irreversibility, cascading effects, or error behavior.

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 has a good inline description, but 'id' has none. The description supplies no meaning for either — it does not say what an id refers to (task node UUID vs. ref_id) or when the confirmation escape hatch should be used. It therefore fails to compensate for the undocumented half of the schema.

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 the tool name repeated ('api_task_nodes_destroy') with no verb or resource phrasing in prose. An agent can infer 'delete a task node' only by parsing the identifier itself, and nothing distinguishes it from the many sibling *_destroy tools. This is the tautology case, not a stated purpose.

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 alternatives such as ciso_assistant_api_task_nodes_partial_update or the remove_evidence variant. The agent is left to infer the entire decision context from the name and the destructiveHint.

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