Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api representatives destroy

ciso_assistant_api_representatives_destroy
DestructiveIdempotent

Permanently removes a representative by ID from CISO Assistant; use the confirm flag when a client cannot answer the destructive-operation prompt.

Instructions

API endpoint that allows representatives 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_representatives_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.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=true, so the safety profile is available structurally. The description adds nothing beyond that — it never says a representative is permanently deleted, whether deletion cascades to linked entities/representatives relationships, or what error a missing id returns. It does not directly contradict the annotations, so no contradiction flag, but it is actively uninformative for a destructive tool.

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, front-loaded sentence with no filler, so it reads cleanly. However, its only sentence is boilerplate that conveys no tool-specific information, which is under-specification rather than genuine conciseness.

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

Completeness3/5

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

The tool has no output schema and only two parameters, so the description carries less burden. Still, for an irreversible delete it should say what resource is removed and any cascade/permission implications; the annotations cover the danger hint, but the prose leaves the agent without operational context.

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 well documented in the schema, but `id` has no description at all. The prose adds no meaning about what `id` identifies or when `confirm` should be set, so it fails to compensate for the uncovered parameter.

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 representatives to be viewed or edited" is generic DRF boilerplate that never states the actual operation. The tool name and title say destroy, but the description describes viewing/editing, and it gives no way to distinguish this from the dozens of sibling *_destroy endpoints.

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 prerequisite/permission note, and no mention of alternatives such as ciso_assistant_api_representatives_partial_update or _retrieve. Worse, the "viewed or edited" framing points an agent toward read/update use cases even though this is the deletion endpoint.

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