Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api integrations configs destroy

ciso_assistant_api_integrations_configs_destroy
DestructiveIdempotent

Deletes an integration configuration by ID, with optional confirmation for destructive operations and cleanup of obsolete API integrations.

Instructions

API endpoint for creating, viewing, updating, and deleting Integration Configurations.

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_integrations_configs_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

C2.1/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 that deletion is irreversible, whether dependent sync mappings are affected, or what a repeat call returns (idempotency semantics). Worse, it attributes create/read/update behavior to a delete-only endpoint, which misdirects rather than informs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, so it is not bloated, but the space is spent on a generic inventory of CRUD verbs instead of the one useful fact (this call deletes). Brevity here comes at the cost of precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, idempotent, open-world endpoint with no output schema and half its parameters undocumented, the description should at minimum state that it permanently removes an Integration Configuration, note the `confirm` escape hatch for non-interactive clients, and point at retrieval siblings for pre-check. None of that is present.

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%: `confirm` is documented in the schema, but `id` (the sole required parameter) has no description anywhere, and the tool description does not compensate by explaining what identifier is expected or where to obtain it. Neither parameter is mentioned in the description.

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 CRUD boilerplate: "API endpoint for creating, viewing, updating, and deleting Integration Configurations." It names the resource but never states that this specific tool only deletes a single config, and it enumerates verbs that belong to the sibling tools (integrations_configs_create, _list, _retrieve, _update). Only the tool name "destroy" disambiguates.

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?

No when-to-use guidance, no when-not-to-use, no reference to alternatives such as partial_update or the cascade_info/retrieve siblings for inspecting before removal. The only hint is the word "deleting" buried in a list of four verbs.

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