Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api task nodes remove evidence create

ciso_assistant_api_task_nodes_remove_evidence_create
Destructive

Removes evidence from a specified task node in CISO Assistant; set confirm to acknowledge the destructive operation.

Instructions

api_task_nodes_remove_evidence_create

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

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally and the description does not contradict it. The description adds nothing beyond that: it does not say what record is actually removed, whether the evidence object itself survives, what permissions are required, or whether the effect is reversible.

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 fragment with zero structure or front-loading, so brevity here reflects under-specification rather than economy. Nothing about the string helps an agent decide or prepare a call.

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, non-idempotent write tool with no output schema and an undocumented required id, the definition supplies no information an agent can act on. Every specification detail an agent needs is missing.

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 50%: the 'confirm' parameter carries a clear schema description, but the required 'id' parameter has no description at all, and the description text gives no clue whether it is the task node id, the evidence id, or the link id. With half the schema undocumented, the description was the place to compensate and does not.

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 the tool's own identifier string restated verbatim: "api_task_nodes_remove_evidence_create". It names the resource path but never states in plain language what the operation does, and the trailing "_create" conflicts with the "remove evidence" reading, so an agent cannot say confidently whether this deletes an evidence link or creates a removal record.

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 preconditions, and no mention of any alternative. The sibling list contains many candidates in the same family (ciso_assistant_api_task_nodes_destroy, ciso_assistant_api_evidences_destroy, ciso_assistant_api_task_nodes_evidences_list), and nothing indicates which one applies when an agent wants to unlink evidence from a task node.

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