Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api perimeters destroy

ciso_assistant_api_perimeters_destroy
DestructiveIdempotent

Deletes a CISO Assistant perimeter by ID, with optional confirmation for destructive operations.

Instructions

API endpoint that allows perimeters 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_perimeters_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.5/5.0
Behavior1/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, idempotentHint=true and openWorldHint=true, but the description says the endpoint is for 'viewed or edited' — which implies a read/update operation and directly conflicts with a non-read-only, destructive hint. It says nothing about irreversibility, permission requirements, or what the 'confirm' parameter protects against. This is an annotation contradiction, not just a gap.

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, so there is little waste, but the sentence is pure boilerplate that conveys no usable information. Brevity here reflects under-specification rather than efficient communication.

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, irreversible delete with no output schema, an agent needs to know what gets removed and how confirmation works; the description supplies neither and instead mischaracterizes the operation as view/edit. The only safety signal comes from annotations, which the description undercuts.

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 carries a good schema description, but 'id' has none. The description contributes zero parameter meaning — it never mentions the identifier, the confirmation flag, or when confirmation is required. With half the parameters undocumented in the schema, the description needed to compensate and 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 reads as generic Django REST framework boilerplate: 'API endpoint that allows perimeters to be viewed or edited.' It names the resource (perimeters) but describes view/edit actions, while the tool is actually a destroy/delete endpoint. An agent reading only the description would not know this tool deletes a perimeter, and it does not distinguish itself from the many sibling retrieve/update/partial_update perimeter 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?

There is no when-to-use guidance, no mention of alternatives such as ciso_assistant_api_perimeters_retrieve or _update, and no prerequisites. Worse, the implied usage ('viewed or edited') points an agent toward exactly the wrong situation for a destructive call, so the guidance is actively misleading rather than merely absent.

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