Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm operational scenarios destroy

ciso_assistant_api_ebios_rm_operational_scenarios_destroy
DestructiveIdempotent

Permanently delete an EBIOS RM operational scenario in CISO Assistant by ID, with an optional confirmation flag for destructive operations.

Instructions

api_ebios_rm_operational_scenarios_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_operational_scenarios_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 safety profile is covered elsewhere. The description adds nothing beyond that: no statement of what is deleted, whether cascading deletes of related EBIOS RM objects occur, whether permissions are required, or how the 'confirm' flag interacts with the destructive call. It contributes zero behavioral context.

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-like string with no wasted words, but the brevity comes from under-specification rather than economy. There is no front-loaded explanation of purpose, target, or effect, so 'concise' here is not a virtue.

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 mutation on an EBIOS RM entity with no output schema, no annotation-independent explanation, and half its parameters undocumented. An agent cannot determine what object it targets, what gets removed, or what happens on failure. The definition is essentially incomplete for the operation's complexity.

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%: 'confirm' is documented in the schema but 'id' is a bare string. The description does not explain that 'id' is the operational scenario identifier, nor does it clarify when the confirmation prompt is required or how to obtain the id. With half the parameters undocumented in the schema, the description should 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 is just the tool name echoed back: 'api_ebios_rm_operational_scenarios_destroy'. It does convey a resource (EBIOS RM operational scenarios) and a mutation verb implied by 'destroy', but only by restating the identifier with zero natural-language elaboration. It gives no help distinguishing this from the many sibling destroy endpoints such as operational_scenarios_update or strategic_scenarios_destroy.

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, and no caution about deletion scope. With dozens of sibling *_destroy tools in this API, an agent gets no routing signal at all beyond the name. The description actively fails to tell the agent when deletion is appropriate versus updating or archiving.

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