Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api resilience business impact analysis destroy

ciso_assistant_api_resilience_business_impact_analysis_destroy
DestructiveIdempotent

Permanently deletes a resilience business impact analysis by ID, requiring confirmation to prevent accidental removal of critical risk data.

Instructions

api_resilience_business_impact_analysis_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_business_impact_analysis_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 fields. The description adds nothing beyond them: it does not state what gets deleted (the record and its children), whether deletions cascade, or what permissions are required, so it earns little credit.

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 brevity here reflects under-specification rather than efficiency: a single identifier string conveys no actionable information and is not front-loaded with any verb, scope, or consequence.

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 half-documented parameters, the description should explain the target entity, the effect, and the confirmation behavior. It supplies none of that, leaving the agent entirely dependent on a slug and the annotations.

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?

With only 50% schema description coverage, the description needs to compensate, but it provides no parameter information at all. The 'confirm' parameter is documented in the schema, while 'id' is undocumented in both places and the description does not even clarify that it is the identifier of the BIA record to delete.

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 the tool name repeated verbatim ('api_resilience_business_impact_analysis_destroy') with no verb-object sentence explaining what it does. A reader can infer deletion of a business impact analysis record, but that inference comes entirely from the name/slug, not from descriptive prose, and nothing distinguishes it 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 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, and no mention of alternatives such as the sibling list/retrieve/partial_update or batch_action_create tools. The only hint of usage comes from the 'destroy' suffix in 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