Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api asset capabilities destroy

ciso_assistant_api_asset_capabilities_destroy
DestructiveIdempotent

Permanently deletes an asset capability record by ID, with confirmation required when the client cannot prompt.

Instructions

api_asset_capabilities_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_capabilities_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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds nothing beyond that — no mention of what is deleted, cascade effects on linked assets, permission requirements, or whether deletion is recoverable.

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?

This is not conciseness but under-specification: a single identifier token with no sentence structure, no front-loaded purpose, and no information an agent can act on. Nothing was trimmed because nothing was written.

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 mutation with no output schema and an undocumented required id parameter, the description is entirely inadequate — it conveys no consequence, no scope, and no safety context that the agent would need before calling it.

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 only 50%: the 'confirm' parameter is documented in the schema, but 'id' has no description anywhere. The description supplies no meaning for either parameter, so it fails to compensate for the coverage gap on the required identifier.

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 name 'api_asset_capabilities_destroy' with no elaboration. It restates the identifier rather than stating a verb+resource in prose, and it does nothing to distinguish this destroy of asset capabilities from the dozens of near-identical *_destroy siblings.

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, no warning about when not to call it, and no pointer to the paired create/update/list siblings. The agent must infer everything from the name alone.

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