Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api requirement assessments destroy

ciso_assistant_api_requirement_assessments_destroy
DestructiveIdempotent

Deletes a requirement assessment by ID, with an optional confirm flag for destructive operations when client confirmation is unavailable.

Instructions

API endpoint that allows requirement assessments 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_requirement_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.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that and its "viewed or edited" framing actively obscures that this call permanently removes a requirement assessment; it never mentions irreversibility, cascade effects, or prerequisites.

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, but it is uninformative boilerplate that does not earn its place: the one fact that matters — that this is a destructive delete — is absent.

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 endpoint with no output schema, the description should state that the record is permanently deleted and mention the confirm flag's role. Instead it describes viewing/editing, leaving the agent without the essential behavioral fact.

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 is documented in the schema, but id is a bare string. The description does not clarify that id identifies the requirement assessment to delete, adding no meaning beyond the schema.

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 the endpoint "allows requirement assessments to be viewed or edited," which restates a generic CRUD boilerplate and never says the tool deletes anything. The verb does not match the resource operation named in the tool name (destroy), so an agent cannot confidently tell this apart from the many *_retrieve and *_update siblings.

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 or when-not-to-use guidance at all, and the phrasing points toward viewing/editing, which is the opposite of the guidance an agent needs before calling a destroy endpoint that has many retrieve/update siblings.

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