Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api document attachments destroy

ciso_assistant_api_document_attachments_destroy
DestructiveIdempotent

Deletes a document attachment by ID and requires explicit confirmation to authorize the destructive operation when the client cannot answer a confirmation prompt.

Instructions

API endpoint for serving document attachment files.

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_document_attachments_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 endpoint as 'serving' files, implying a safe read. The description adds nothing about what gets removed, whether deletion is soft or hard, cascade effects on document revisions, or required permissions — and its framing runs counter to the annotations.

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 a single short sentence, which is structurally fine, but the sentence is inaccurate boilerplate that does not earn its place — brevity does not help when the content misroutes the agent.

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, idempotent delete operation with no output schema, the description should at minimum state what is deleted, irreversibility, and permission implications. Instead it contains only a generic generator string that describes the opposite kind of operation, leaving the agent with nothing usable beyond 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?

The schema already documents the `confirm` parameter thoroughly, but `id` has no description and coverage sits at 50%. The description supplies no meaning for either parameter, so it fails to compensate for the undocumented identifier of the attachment being destroyed.

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 is 'for serving document attachment files', which describes a read/download operation, while the tool name, title, and annotations all indicate destruction (destroy, destructiveHint=true). An agent reading only the description would conclude this retrieves files rather than deletes them, so the stated purpose is actively misleading.

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 call this versus the many siblings such as ciso_assistant_api_document_attachments_create, _retrieve, or _file_retrieve. No prerequisites, no exclusion conditions, and no warning about the effect on the parent document are given.

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