Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api evidences destroy

ciso_assistant_api_evidences_destroy
DestructiveIdempotent

Deletes an evidence record by ID in CISO Assistant. Set confirm to true to authorize this destructive operation when the client cannot answer a confirmation prompt.

Instructions

API endpoint that allows evidences 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_evidences_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.1/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description claims the endpoint is for viewing or editing evidence, directly contradicting the destructive nature. It says nothing about what is irreversibly removed, whether attached files/revisions are also deleted, or required authorization.

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, so there is no padding, but the sentence is boilerplate template text that conveys no actionable information and actively misleads. Brevity here comes from under-specification rather than economy.

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 delete endpoint with a confirmation parameter and no output schema, the description supplies none of the required context: no statement of permanence, no confirmation semantics, no error behavior. It is entirely inadequate for the risk profile of the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the required 'id' parameter has no schema description, and the description adds no meaning about what the id identifies or how it is obtained. The 'confirm' flag is documented in the schema but never referenced or explained in the description.

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 evidences to be viewed or edited', which misstates the operation: the tool name ends in _destroy and it deletes an evidence record by id. The verb is wrong and the agent would conclude this is a read/update tool rather than a deletion.

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 at all, no mention that this permanently removes an evidence object, and no routing to alternatives such as ciso_assistant_api_evidences_update or the evidence-revision deletion tools. The only implied usage ('view or edit') is the opposite of what the tool does.

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