Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm feared events destroy

ciso_assistant_api_ebios_rm_feared_events_destroy
DestructiveIdempotent

Deletes an EBIOS RM feared event by ID, enabling removal of obsolete or incorrect risk scenarios from a CISO Assistant assessment.

Instructions

api_ebios_rm_feared_events_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_feared_events_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.3/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the bar is low, but the description adds nothing at all — not what gets deleted, not cascade consequences, not the confirm prompt semantics. It is a bare restatement of the name.

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?

There is no unnecessary wording, but that is because there is essentially no content — a single identifier-shaped string. This is under-specification, not conciseness, and nothing is front-loaded because nothing is said.

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 delete operation on an EBIOS RM feared event with no output schema and no annotations explaining cascade behavior. An agent cannot determine from this definition what will be removed or whether related objects (attack paths, operating modes) are affected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the 'id' parameter has no description in the schema, and the 'confirm' flag is documented only by the schema. The description explains neither, 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?

The description is literally the tool identifier restated ('api_ebios_rm_feared_events_destroy'), which is tautological. The name does hint at deleting an EBIOS RM feared event, but the description itself states no verb-plus-resource purpose and does nothing to distinguish it from the many sibling *_destroy tools.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as partial_update or the batch_action variants. An agent gets zero routing information.

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