Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api organisation objectives destroy

ciso_assistant_api_organisation_objectives_destroy
DestructiveIdempotent

Deletes a CISO Assistant organisation objective by ID and supports explicit confirmation when the destructive action requires approval.

Instructions

api_organisation_objectives_destroy

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_organisation_objectives_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
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried by structured data and the description does not contradict it. However, the description adds nothing beyond that — not what is destroyed, whether child records cascade, whether the objective is archived or hard-deleted, or what permission is required. For a destructive operation this is a real gap even with annotations present.

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?

The text is short but this is under-specification, not conciseness — it is a bare token with no front-loaded purpose sentence. Length itself is not the problem; the absence of any useful sentence is.

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 only partial schema coverage, the definition supplies nothing an agent needs: no statement of effect, no irreversibility or cascade warning, no confirmation workflow. Everything must be inferred from the name and annotations alone.

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 50%: the `confirm` parameter is documented in the schema, but `id` has no description and the tool description does not explain that it identifies the organisation objective to delete. With coverage below the 80% threshold, the description was expected to compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is the literal string "api_organisation_objectives_destroy", an identifier restated verbatim from the tool name and title. It states no verb-plus-resource sentence an agent could read, and gives no basis for distinguishing this from the many sibling `_destroy` tools such as `ciso_assistant_api_organisation_issues_destroy`.

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 exclusion of alternatives, and no mention of the relevant siblings (`organisation_objectives_cascade_info_retrieve`, `organisation_objectives_update`, the batch_action sibling). An agent has no textual signal for choosing this over those tools.

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