Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api requirement assignments destroy

ciso_assistant_api_requirement_assignments_destroy
DestructiveIdempotent

Deletes a requirement assignment by ID, removing the link between a requirement and its assigned entity; confirm to complete the destructive removal.

Instructions

API endpoint that allows requirement assignments 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_assignments_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

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not required to re-state that the operation is destructive. But a destroy endpoint's description should at minimum say it deletes the identified record, and this one instead says 'viewed or edited', adding no information and steering the agent away from the destructive nature the annotations declare. The only useful signal about confirmation lives in the schema's confirm parameter, not the description.

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?

One short, front-loaded sentence with no filler, so it is structurally efficient. The problem is under-specification rather than verbosity: the single sentence carries no operation-specific content and is misleading for its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, id-requiring delete with no output schema, the description should explain what record is removed and note the confirm flag for irreversible deletion. Instead it describes a view/edit endpoint, leaving the agent dependent entirely on annotations and the raw confirm parameter to understand the tool.

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 has no description at all. The description does not clarify that id identifies the requirement assignment to delete, so it does not compensate for the coverage gap. Baseline 3 would apply if the schema covered the parameters; it 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 generic DRF boilerplate: 'API endpoint that allows requirement assignments to be viewed or edited.' It never states the actual operation, which is deletion of a requirement assignment by id, and the word 'viewed' points the agent at the opposite behavior. Only the tool name's 'destroy' suffix disambiguates it from siblings like requirement_assignments_list or requirement_assignments_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 the alternative update/partial_update/set_status operations, and no warning that this is irreversible. Worse, 'viewed or edited' actively invites the agent to reach for this tool to read data, which is the wrong selection.

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