Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api resilience asset assessments destroy

ciso_assistant_api_resilience_asset_assessments_destroy
DestructiveIdempotent

Permanently deletes a resilience asset assessment by ID and requires explicit confirmation to prevent accidental removal.

Instructions

api_resilience_asset_assessments_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_resilience_asset_assessments_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.5/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 known without the description. The description adds no behavioral context of its own — nothing about whether the deletion cascades to related assessments, whether it is recoverable, or what confirm does in practice.

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 short but that is under-specification, not conciseness — a single bare identifier carries zero information and is not front-loaded around any actionable statement.

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, open-world operation with no output schema and partial parameter documentation, the description should carry substantial weight about irreversibility and scope. It provides none of that, so an agent cannot safely decide to call this tool from the definition alone.

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 only 50%: the confirm parameter is documented in the schema but id has no description at all. The description compensates for neither gap, leaving it to the schema alone to convey that id identifies the assessment record to delete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the raw operation identifier repeated verbatim ('api_resilience_asset_assessments_destroy'), with no verb-plus-resource phrasing an agent could act on. It adds nothing beyond the tool name and does not distinguish this destroy from the dozens of 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 guidance on when to use this tool, no prerequisites, no mention of the confirm parameter, and no reference to alternative sibling tools such as the asset assessments update or retrieve variants.

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