Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api journey steps destroy

ciso_assistant_api_journey_steps_destroy
DestructiveIdempotent

Deletes a journey step by ID in CISO Assistant, with optional confirmation for destructive operations.

Instructions

api_journey_steps_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_journey_steps_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.1/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds no behavior context at all, such as cascade effects on linked objects, permission requirements, or irreversibility, despite 'destroy' operations carrying real risk.

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 and has zero noise, but that brevity comes from under-specification rather than economy. There is no front-loaded statement of purpose or any structure to speak of.

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 operation on a nested domain object, the definition should explain what is removed, what happens to related journey data, and how 'confirm' interacts with client confirmation prompts. It provides none of this, leaving the annotation and schema fragments to carry the entire burden.

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 only 50%: the 'id' parameter has no description in the schema, and the description provides nothing to compensate. The meaning of the confirmation parameter and the identifier format are left entirely unexplained by the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is literally the tool's own name restated ('api_journey_steps_destroy'), which is a tautology. It identifies no verb, resource, or scope beyond what the identifier already implies, and gives an agent no way to distinguish it from the many other *_destroy siblings.

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 guidance about when to use this tool, what a journey step is, when deletion is appropriate, or which alternative (cascade_info_retrieve, partial_update, batch_action_create) an agent should prefer. Nothing is stated or even implied.

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