Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api ebios rm ro to destroy

ciso_assistant_api_ebios_rm_ro_to_destroy
DestructiveIdempotent

Permanently deletes an EBIOS RM RO/TO couple by ID; set confirm when the client cannot answer a confirmation prompt.

Instructions

api_ebios_rm_ro_to_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_ro_to_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.7/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 carried by structured data rather than the description. The description adds nothing about what is destroyed, whether deletion cascades to dependent EBIOS RM objects, or whether the operation is reversible, which is exactly the context a destructive tool 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 a single short token with no wasted words, but that is under-specification rather than conciseness. There is no front-loaded statement of action or scope for the reader to anchor on.

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 on an EBIOS RM RO/TO entity with no output schema, the description should explain what the resource is, what gets removed, and what confirmation implies. None of that is present, leaving the definition wholly inadequate for the tool's complexity.

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 documented in the schema itself, while 'id' has no description anywhere. The description supplies no additional meaning about what identifier is expected (an RO/TO object id) or how 'confirm' interacts with the deletion flow, 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 the identifier 'api_ebios_rm_ro_to_destroy' repeated verbatim, which merely restates the name/title. It conveys no verb-plus-resource explanation beyond the embedded token 'destroy', and 'ro_to' is unexplained jargon an agent cannot resolve without outside knowledge.

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 prerequisites, and no mention of alternatives among the many sibling destroy tools (e.g. ciso_assistant_api_ebios_rm_studies_destroy). 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