Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api terminologies destroy

ciso_assistant_api_terminologies_destroy
DestructiveIdempotent

Permanently deletes a terminology by ID in CISO Assistant, requiring explicit confirmation to prevent accidental removal.

Instructions

api_terminologies_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_terminologies_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, readOnlyHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: no mention of cascade deletion of dependent objects, permission requirements, or 404 behavior on unknown ids, which is the kind of context a destructive tool should surface.

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 identifier repeated as prose: zero waste, but also zero content. This is under-specification rather than conciseness, since no information beyond the tool name is conveyed.

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 mutation operating on a referenced object, an agent needs to know what is deleted, whether related objects are cascaded, and how confirmation works. None of that is present, and there is no output schema to fall back on.

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' parameter is documented in the schema itself, while 'id' carries no description anywhere. The description does not compensate at all, and it says nothing about whether 'confirm' must be true for destructive execution or how the id is obtained.

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 literally the tool's name, 'api_terminologies_destroy', which only restates the identifier. An agent must decode 'destroy' plus 'terminologies' to infer a deletion of a terminology record, and nothing distinguishes it from the dozens of sibling *_destroy tools beyond the literal resource token.

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 whatsoever on when to call this versus alternatives such as terminologies_partial_update, terminologies_cascade_info_retrieve (which would reveal what a delete would cascade to), or the batch_action sibling. No prerequisites, no warnings about irreversibility are given in 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