Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api loaded libraries destroy

ciso_assistant_api_loaded_libraries_destroy
DestructiveIdempotent

Deletes a loaded library from CISO Assistant by ID, requiring explicit confirmation for this destructive action.

Instructions

api_loaded_libraries_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_loaded_libraries_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

C2/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 contributes nothing extra: no statement of what is removed, whether linked requirements/assessments are affected, or whether the operation is reversible.

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 technically short, but the brevity comes from under-specification rather than economy. A single snake_case token with no sentence structure provides no front-loaded explanation an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-read-only operation with no output schema, the definition should at minimum state the target object and the effect of the confirm flag. None of that is present, leaving the agent to infer destructive consequences entirely from annotations and the bare schema.

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 description coverage is 50%: the 'confirm' parameter is documented inline, but 'id' has no description and the tool description does not compensate by saying which identifier is expected (loaded library id vs. stored library id). The description adds zero semantics beyond the schema.

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 literal identifier "api_loaded_libraries_destroy", which only restates the tool name. It conveys no verb/resource framing an agent could not already infer from the name, and gives no hint of what a 'loaded library' is or that it is being deleted from the tenant's library set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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. With siblings such as ciso_assistant_api_stored_libraries_unload_create and ciso_assistant_api_loaded_libraries_batch_action_create present, an agent receives no help distinguishing a single destructive delete from an unload or bulk action.

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