Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api asset class destroy

ciso_assistant_api_asset_class_destroy
DestructiveIdempotent

Permanently delete an asset class from CISO Assistant by specifying its ID. Use the confirm flag to bypass client confirmation prompts for destructive operations.

Instructions

api_asset_class_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_asset_class_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, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no statement of what gets removed, whether child or linked records are affected, whether the delete is recoverable, or what errors look like. It does not contradict the annotations, but it contributes zero behavioral value.

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?

The text is a single token, so it is technically brief, but this is under-specification rather than conciseness. There is no structure, no front-loaded verb-and-resource statement, and nothing that earns its place.

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, irreversible-by-default operation in a large API surface with no output schema, the description should at minimum say what is deleted and warn about cascading effects on assets. It supplies none of that, leaving the definition inadequate for the tool's risk profile.

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` flag is well documented in the schema, but `id` carries no description anywhere. The description does not explain that `id` is the asset-class identifier, whether it is a UUID or ref, or how confirmation behaves when the client can answer a prompt.

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?

"api_asset_class_destroy" restates the tool name and title without adding a verb, object, or scope in prose. An agent can infer a deletion of an asset class from the slug, but the description itself supplies no clarifying statement, and it does nothing to distinguish this from the many sibling *_destroy tools.

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 or permissions, and no pointer to alternatives (for example, whether to check cascade_info_retrieve before deleting). The agent must infer everything from the name.

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