Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm elementary actions destroy

ciso_assistant_api_ebios_rm_elementary_actions_destroy
DestructiveIdempotent

Deletes an EBIOS RM elementary action by ID, with an optional confirm flag for destructive operations.

Instructions

api_ebios_rm_elementary_actions_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_elementary_actions_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, openWorldHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond them: no statement about what is removed, whether cascade deletion of dependent attack paths/operating modes occurs, or permission requirements — a notable gap for a destructive endpoint.

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 identifier with zero explanatory content — not verbose, but under-specified rather than concise. There is no front-loaded statement of what the tool does or what it affects.

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?

For a destructive, open-world delete operation with no output schema and partial parameter documentation, the description provides nothing an agent needs: no object scope, no cascade/irreversibility note, no confirmation semantics. The definition is essentially empty.

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 50%: the `confirm` parameter is well documented in the schema, but `id` has no description, and the description supplies no clarification of which object the id identifies. With half the parameters undocumented, the description 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 just the tool name in snake_case ("api_ebios_rm_elementary_actions_destroy"), a tautology that restates the title. An agent can infer a delete operation on EBIOS RM elementary actions only by parsing the identifier, and nothing distinguishes this from the many sibling `_destroy` tools beyond the resource segment.

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 (e.g. `ebios_rm_elementary_actions_partial_update` or `batch_action_create`), and no preconditions. The only hint that this is destructive comes from annotations, not the description.

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