Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api assets destroy

ciso_assistant_api_assets_destroy
DestructiveIdempotent

Deletes a CISO Assistant asset by ID through the API, with an optional confirmation flag for destructive operations.

Instructions

API endpoint that allows assets to be viewed or edited.

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_assets_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.6/5.0
Behavior1/5

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

Annotations declare destructiveHint=true, idempotentHint=true and openWorldHint=true, while the description frames the tool as a view/edit endpoint. That framing conceals the fact that a call irreversibly removes an asset and gives no context on side effects such as linked controls or requirement assessments. Describing a delete endpoint as a viewing/editing endpoint contradicts the destructive annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, front-loaded sentence with no filler, so it is compact. However, brevity is achieved by omitting the crucial fact, so the sentence earns its place only in the sense of being short.

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 endpoint with no output schema, the description must carry the entire burden: it should state the deletion semantics, the confirmation requirement, and any cascade behavior. None of that is present, leaving an agent unable to call it safely.

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, and 'id' has no description anywhere. The description adds nothing to either parameter, not even what identifier 'id' expects (asset UUID vs. ref_id) or why confirmation is required.

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 says the endpoint 'allows assets to be viewed or edited,' which names the resource but misidentifies the operation. The tool is named *_destroy and its only meaningful action is deletion, so the stated verb set (view/edit) actively points the agent at the wrong operation and does not distinguish it from siblings like ciso_assistant_api_assets_retrieve or ciso_assistant_api_assets_update.

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 mention of prerequisites, and no reference to any alternative. The presence of a 'confirm' parameter implies a confirmation workflow, but the description never explains when deletion is appropriate versus updating or archiving an asset.

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