Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api findings assessments destroy

ciso_assistant_api_findings_assessments_destroy
DestructiveIdempotent

Permanently delete a findings assessment by ID to remove outdated or incorrect records; optionally confirm the destructive action when the client cannot prompt.

Instructions

api_findings_assessments_destroy

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_findings_assessments_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 already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is known. The description adds nothing beyond them: no statement of what records are removed, whether dependent findings/assessments are cascade-deleted, whether the operation is recoverable, or what permissions are needed. It provides zero behavioral value for a destructive tool.

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?

The text is brief, but its brevity comes from under-specification rather than economy — it is a single identifier string with no front-loaded intent, scope, or warning. There is nothing to trim and nothing to reward.

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-read-only endpoint whose only required parameter is an undocumented id, the description should state what is deleted, whether the deletion cascades to related findings, and whether it is reversible. None of this is present, and there is no output schema to fall back on.

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 description coverage is only 50%: the required 'id' parameter has no description in the schema, and the description supplies none either, so the caller never learns which identifier (finding id, assessment id, or nested assessment record) is expected. Only 'confirm' is documented in the schema, and the description contributes nothing to disambiguate destruction semantics or the confirm flag's interaction with the client prompt.

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 only 'api_findings_assessments_destroy', which merely restates the tool name and title without a verb+resource statement in prose. An agent gets no explanation of what a 'findings assessment' is or what destroying one means. It cannot distinguish this tool from the ~100 sibling *_destroy tools beyond the name segments.

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, when-not-to-use, or alternative guidance whatsoever. The sibling list is dominated by other *_destroy endpoints plus findings_assessments_batch_action_create and findings_assessments_cascade_info_retrieve, but the description never routes the agent to any of them or states preconditions for 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