Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api security advisories destroy

ciso_assistant_api_security_advisories_destroy
DestructiveIdempotent

Delete a security advisory by ID; use the confirm flag when the client cannot answer a destructive-operation confirmation prompt.

Instructions

API endpoint that allows security advisories 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_security_advisories_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.8/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 frames the endpoint as one that 'views or edits' records, omitting and effectively contradicting the destructive nature. It says nothing about irreversible data loss, permission requirements, or what cascade effects occur.

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, but that brevity reflects templated boilerplate rather than front-loaded precision. It is concise without being informative.

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 mutation tool with no output schema and half-undocumented parameters, the description is wholly inadequate. An agent could invoke this thinking it views or edits data, causing irreversible deletion.

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?

With only 50% schema description coverage, the description must compensate, but it adds nothing. The required `id` parameter is undocumented in both schema and description, and the `confirm` flag's confirmation semantics are left entirely to the schema text.

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 names the resource (security advisories) but describes the operation as 'viewed or edited', which does not match a destroy/delete endpoint. It reads as boilerplate viewset documentation and does not distinguish this tool from siblings such as ciso_assistant_api_security_advisories_retrieve or _update.

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, and no reference to alternative tools. An agent gets no signal about when deletion is appropriate versus when a list/retrieve/partial_update sibling should be used.

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