Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api evidence revisions delete attachment create

ciso_assistant_api_evidence_revisions_delete_attachment_create
Destructive

Deletes an attachment from an evidence revision. Set confirm=true to proceed when the client cannot display a confirmation prompt.

Instructions

API endpoint that allows evidence revisions 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_evidence_revisions_delete_attachment_create"
  }
}

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 and readOnlyHint=false, but the description adds nothing about what is removed, whether it is reversible, or required permissions; worse, 'viewed or edited' actively downplays the destructive attachment deletion. The confirm parameter's role is only explained by the schema, not the description.

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 wasted words and is front-loaded, but its brevity comes from being a generic template rather than from precision, so the structure is fine while the content is uninformative.

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, non-idempotent operation with no output schema and only half its parameters documented, the definition should explain what gets deleted and what the confirm flag guards against. The one generic sentence leaves the agent materially under-informed before calling a destructive endpoint.

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 'confirm' flag is documented in-schema but 'id' is not. The description says nothing about either parameter, so it does not compensate for the undocumented id (presumably the evidence revision or attachment identifier) at all.

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 says only that evidence revisions can be 'viewed or edited,' which neither names the delete-attachment action in the tool name nor distinguishes it from the many evidence-revision siblings (retrieve, update, partial_update, destroy, upload). It is generic boilerplate that mischaracterizes what the endpoint actually does, so an agent cannot infer the operation from the text.

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 mention of prerequisites (such as needing the revision id and an existing attachment), and no reference to alternatives like evidence_revisions_attachment_retrieve or evidence_revisions_destroy. The agent is left to guess the context entirely from the tool 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