Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api stored libraries destroy

ciso_assistant_api_stored_libraries_destroy
DestructiveIdempotent

Deletes a stored library by ID, with an optional confirmation flag to authorize the destructive removal.

Instructions

api_stored_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_stored_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

D1.3/5.0
Behavior1/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 known. The description adds nothing beyond that: it does not say whether deletion cascades to loaded libraries or frameworks derived from the stored library, nor whether it is reversible. It does not contradict the annotations, but it contributes zero behavioral context.

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, but this is under-specification rather than concision; the single token carries no information the tool name did not already convey, and there is no structure or front-loaded explanation.

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?

This is a destructive, open-world, idempotent delete on a domain object that feeds other libraries, with no output schema and only partially documented parameters. The description supplies none of the context an agent would need to invoke it safely, such as what a stored library is, what gets removed, or how it relates to unload.

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 coverage is 50%: the confirm parameter is documented in the schema, but id has no description at all. The description provides no explanation of what id identifies or whether confirm is needed for cascading deletions, so the undocumented half of the schema stays undocumented.

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 "api_stored_libraries_destroy", which restates the tool name in snake_case and nothing more. An agent learns only that some unspecified thing is destroyed; it cannot tell what a stored library is or how this differs from sibling tools such as stored_libraries_unload_create or loaded_libraries_destroy without inspecting the schema.

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 prerequisite or permission note, and no mention of alternatives. Given the many near-identical destroy siblings (integrations_configs_destroy, loaded_libraries_destroy, stored_libraries_unload_create), the absence of routing guidance is a real hazard.

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