Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api resilience escalation thresholds destroy

ciso_assistant_api_resilience_escalation_thresholds_destroy
DestructiveIdempotent

Delete a resilience escalation threshold by ID to remove outdated alerting rules, with an optional confirmation flag for destructive operations.

Instructions

api_resilience_escalation_thresholds_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_escalation_thresholds_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, readOnlyHint=false, and openWorldHint=true, so the safety profile is fully machine-readable. The description adds nothing beyond that — no statement about cascade effects (a cascade_info_retrieve sibling exists), irreversibility, or required permissions. No contradiction, but zero added behavioral context.

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?

It is one identifier-length string, so there is no wasted wording, but this is under-specification rather than conciseness. It is not front-loaded with any actionable information because it contains none.

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?

A destructive, open-world delete operation with an undocumented required identifier, possible cascade behavior, and no output schema needs far more than a name echo. An agent has nothing to determine impact, prerequisites, or confirmation requirements for a deletion of a resilience configuration object.

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 well documented in the schema itself, but `id` is an undocumented opaque string. The description gives no hint that `id` is the escalation threshold identifier or how to obtain it, so it fails to compensate for the coverage gap.

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 slug repeated: "api_resilience_escalation_thresholds_destroy". It restates the name/title without stating what an escalation threshold is, what deleting one means, or how it differs from sibling operations on the same resource such as resilience_escalation_thresholds_retrieve, _list, _update, or _cascade_info_retrieve.

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 prerequisites, and no alternative named. The extremely dense sibling set (create/retrieve/list/update/batch_action/destroy for the same resilience escalation thresholds resource) makes routing guidance essential, and none is provided.

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