Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm operating modes destroy

ciso_assistant_api_ebios_rm_operating_modes_destroy
DestructiveIdempotent

Deletes an EBIOS RM operating mode by ID and requires confirmation when a client cannot answer a destructive-action prompt.

Instructions

api_ebios_rm_operating_modes_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_operating_modes_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.8/5.0
Behavior2/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. The description adds no behavioral context beyond that: nothing about cascade effects on dependent EBIOs RM objects, permanence, or required permissions. It does not contradict the annotations, but it contributes nothing.

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 short, but brevity here comes from under-specification, not from editing: the single token is a machine identifier with no leading statement of intent. Nothing is front-loaded because there is nothing to front-load.

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 endpoint in a hierarchical EBIOS RM model with no output schema, the description should at minimum state that the record is permanently deleted and whether dependents block or cascade. Neither is present, leaving the agent reliant on annotations and the surrounding tool family.

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?

With schema description coverage at 50%, the `confirm` parameter is documented in the schema while `id` has no explanation in either place. The description does not clarify whether `id` is the operating mode UUID or another identifier, nor when the confirmation flag is actually required.

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 only the operation identifier "api_ebios_rm_operating_modes_destroy", which restates the tool name and title rather than explaining what happens. The word "destroy" plus the resource path hints at deleting an EBIOS RM operating mode, but the agent gets no confirmation of what object is removed or what the operation returns.

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 mention of alternatives such as the partial_update or batch_action siblings, and no prerequisites or warnings. The description is a bare identifier, so the agent must infer everything from the name.

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