Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm stakeholders destroy

ciso_assistant_api_ebios_rm_stakeholders_destroy
DestructiveIdempotent

Deletes a specified EBIOS RM stakeholder by ID from CISO Assistant, with optional confirmation for destructive operations.

Instructions

api_ebios_rm_stakeholders_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_stakeholders_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, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing about consequences — whether deleting a stakeholder cascades to related feared events, strategic scenarios, or study links, or whether permissions are required — which is exactly the context a destructive endpoint needs.

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 that is under-specification rather than conciseness — a single identifier with no front-loaded purpose statement, no constraints, and no useful information.

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 delete with no output schema and a partially documented schema, the description should at minimum state what is removed and any irreversible side effects. Annotations cover the destructive flag, but the description leaves the agent without enough to invoke this safely or correctly.

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 only 50%: the 'confirm' flag is documented in the schema, but 'id' has no description. The description supplies no meaning for either parameter, so it does not compensate for the gap or clarify what object the id refers to.

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 identifier 'api_ebios_rm_stakeholders_destroy' restated verbatim; it adds no verb, resource, or scope beyond what the tool name already encodes. An agent learns only that this relates to EBIOS RM stakeholders and destruction, and gets no differentiation 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 ebios_rm_stakeholders_update or the batch_action variant. The agent must infer entirely on its own when deletion is appropriate versus updating or deactivating a stakeholder.

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