Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api privacy data contractors destroy

ciso_assistant_api_privacy_data_contractors_destroy
DestructiveIdempotent

Deletes a privacy data contractor record by ID, requiring confirmation for this destructive action.

Instructions

API endpoint that allows data contractors 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_privacy_data_contractors_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.6/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the description should confirm and explain the deletion; instead it says the endpoint 'allows data contractors to be viewed or edited', which actively misrepresents the tool as a read/edit operation. Nothing is said about irreversibility, cascading effects, or when the confirm flag is required.

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 one short sentence with no wasted words, but the brevity comes from under-specification rather than economy; the sentence is generic framework boilerplate dumped into the description field.

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 tool with no output schema and a partially documented schema, the description must carry the safety and confirmation burden. It provides none of that and instead describes a different operation.

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 only 50%: the 'confirm' parameter is documented in the schema, but 'id' has no description, and the description supplies no meaning for either. It adds zero information beyond the schema, so it fails to compensate for the coverage gap on the identifier of the record being destroyed.

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 (data contractors) but describes the operation as 'viewed or edited', which is wrong for a destroy endpoint whose name and annotations both signal deletion. An agent could not determine from this sentence that the tool removes a record, and nothing distinguishes it from the many sibling '_retrieve', '_update' or '_partial_update' privacy-data-contractor tools.

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 when-to-use guidance, no statement of prerequisites or irreversibility, no mention of the confirm parameter or of safer alternatives such as updating the contractor instead of deleting it. It reads as generic boilerplate rather than routing information.

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