Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm studies destroy

ciso_assistant_api_ebios_rm_studies_destroy
DestructiveIdempotent

Deletes an EBIOS RM study by ID, using an optional confirm flag for destructive operations when a client cannot answer a confirmation prompt.

Instructions

API endpoint that allows ebios rm studies to be viewed or edited.

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_studies_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 declare destructiveHint=true and readOnlyHint=false, but the description frames the endpoint as viewing/editing, which is a non-destructive framing. With annotations present the bar is lower, but the description not only adds nothing about what gets destroyed or cascaded, it contradicts the safety profile the annotations establish.

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?

One short sentence, but brevity here comes from under-specification rather than economy. The single clause is wasted on generic CRUD boilerplate that does not describe this tool's actual behavior.

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, non-read-only operation with no output schema, the description should cover irreversibility, cascading deletion of child EBIOS RM objects, and permission requirements. None of that is present, so an agent cannot safely decide whether to call it.

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 description coverage is 50%: the confirm parameter is documented in the schema, but id is not, and the description adds no meaning for either. It never references the identifier being destroyed or when the confirmation flag is required, 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 says the endpoint "allows ebios rm studies to be viewed or edited," which is a generic auto-generated docstring rather than a statement of what this specific tool does. The tool name, id parameter, and destructiveHint all indicate deletion, yet the description never mentions deleting; an agent reading only the prose would misidentify the operation.

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 is given, and the phrase "viewed or edited" actively points toward sibling read/update tools (ebios_rm_studies_list, ebios_rm_studies_retrieve, ebios_rm_studies_update) rather than this destroy endpoint. There is no warning about irreversibility or cascade effects, and no exclusion of alternatives.

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