Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm kill chains destroy

ciso_assistant_api_ebios_rm_kill_chains_destroy
DestructiveIdempotent

Deletes an EBIOS RM kill chain by ID, with an optional explicit confirmation for this destructive API operation.

Instructions

api_ebios_rm_kill_chains_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_ebios_rm_kill_chains_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 fully carried by structured data. The description adds no context beyond that: it does not say whether deletion cascades to dependent objects (the existence of a kill_chains_cascade_info_retrieve sibling makes this a real concern), whether it 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?

The single fragment is not verbose, but that is because it is under-specified rather than efficient. There is no front-loaded statement of action, scope or consequence, so the text occupies space without conveying information.

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 an irreversible destructive operation on an EBiOS RM kill chain with no output schema and no description of side effects, cascade behavior, or required confirmation flow. For a high-risk mutation tool, the definition provides nothing beyond annotations and a schema with an undocumented required ID.

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 only 50%: the `confirm` parameter is documented in-schema, but `id` has no description at all and the description supplies no meaning for it. The description does not clarify that `id` is a kill-chain identifier, nor explain the interplay between `confirm` and a destructive delete, so it 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?

"api_ebios_rm_kill_chains_destroy" is a verbatim restatement of the tool name, so the description itself contributes no statement of what the tool does beyond the tautology. The name does encode a resource (EBiOS RM kill chains) and an action (destroy), which is marginally more informative than a bare label, but the description adds nothing an agent could not already read from the identifier.

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 guidance whatsoever on when to call this tool, when not to, or which sibling to use instead. With dozens of sibling tools including ciso_assistant_api_ebios_rm_kill_chains_retrieve, _update, _list and _cascade_info_retrieve, an agent gets no help distinguishing deletion from inspection or update.

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