Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api risk matrices destroy

ciso_assistant_api_risk_matrices_destroy
DestructiveIdempotent

Deletes a risk matrix by ID and requires explicit confirmation for the destructive operation, enabling risk matrix record management via the API.

Instructions

API endpoint that allows risk matrices 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_risk_matrices_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 disclose destructiveHint=true and idempotentHint=true, so the safety profile is known from structured data. The description adds nothing — not what is destroyed, whether dependent objects (risk assessments, scenarios referencing the matrix via risk_matrices_used_retrieve) are affected, nor what permissions or confirmation flow is required beyond the schema's 'confirm' flag.

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?

A single short sentence, so it is not bloated, but it fails the 'every sentence earns its place' test: the sentence conveys boilerplate that actively steers the agent away from the tool's true destructive purpose.

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 no output schema and only partial parameter documentation, the description omits everything an agent needs: that data is permanently removed, what cascades may occur, and how 'confirm' should be used. It is inadequate for the tool's risk level.

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 description coverage is only 50%: the 'confirm' parameter is well documented in the schema, but 'id' is bare, and the description supplies no semantics for either. The description does not compensate for the uncovered parameter by explaining what the identifier refers to or how confirm interacts with the destructive call.

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?

"API endpoint that allows risk matrices to be viewed or edited" is a generic CRUD template that identifies the resource but not the operation. The tool's actual action is deletion (name ends in _destroy, annotations set destructiveHint=true), and the description never says so — a mild misdescription rather than a tautology, since the resource is at least named.

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?

No indication of when to use this versus the many siblings operating on the same resource: risk_matrices_retrieve, risk_matrices_list, risk_matrices_update, risk_matrices_partial_update, risk_matrices_create, risk_matrices_used_retrieve. There is no warning about irreversibility or prerequisites, so an agent has no basis to prefer or avoid it.

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