Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api reference controls destroy

ciso_assistant_api_reference_controls_destroy
DestructiveIdempotent

Permanently deletes a reference control by ID; requires a confirmation flag when the client cannot answer a destructive-operation prompt.

Instructions

API endpoint that allows reference controls to be viewed or edited.

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_reference_controls_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.3/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description frames the tool as viewing/editing. It says nothing about permanent removal of a reference control, its cascading effects, or permission requirements. The description directly contradicts the supplied annotations.

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 with no filler, so structurally it is compact. However, brevity here comes from under-specification and an incorrect claim rather than from efficient, information-dense phrasing.

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 mutation endpoint with two parameters, a confirming flag, and no output schema, the description should at minimum state that it permanently deletes a reference control and note the confirmation requirement. It does neither and instead mislabels the operation.

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 50%: the 'id' parameter has no schema description and the description provides no meaning for it either. The 'confirm' flag's purpose is documented only in the schema. The description adds no parameter semantics whatsoever.

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 says the endpoint allows reference controls to be 'viewed or edited', but the tool name and annotations identify this as a destroy (delete) endpoint. The stated purpose is misleading rather than merely vague, so an agent cannot trust it to know what the tool does.

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, when not to, or which sibling (e.g. reference_controls_retrieve, reference_controls_update) is the alternative. Worse, 'viewed or edited' actively routes the agent toward read/update semantics when the correct action is deletion.

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