Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api timeline entries destroy

ciso_assistant_api_timeline_entries_destroy
DestructiveIdempotent

Permanently deletes a timeline entry by its ID from CISO Assistant, with an optional confirm flag to validate the destructive action when prompts are unavailable.

Instructions

api_timeline_entries_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_timeline_entries_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/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered externally. The description adds nothing beyond that - no mention of permanence, cascade effects, permissions required, or what happens to dependent records. It does not contradict the annotations, but it contributes zero behavioral context.

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 a single machine-generated token with no sentence structure and no front-loaded explanation. It is not verbose, but it is under-specified rather than concise - nothing in it earns its place because it duplicates the tool name.

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?

This is a destructive mutation with a required identifier and a confirmation flag, and no output schema to explain results. Given that complexity, the definition provides nothing an agent needs: not what a timeline entry is, not whether deletion is recoverable, and not what the response contains.

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%: 'id' has no description at all, while 'confirm' is documented inline in the schema. The description does not explain what identifier 'id' expects (timeline entry UUID, integer, related object id) or how confirmation semantics work, so it fails to compensate for the documented gap.

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 merely the slug 'api_timeline_entries_destroy' repeated verbatim, which is a tautological restatement of the tool name and title. An agent can only infer a delete operation on timeline entries from the slug itself; the description contributes no verb, resource, or scope information of its own.

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 guidance about when to delete a timeline entry versus updating it, nor any reference to sibling tools such as ciso_assistant_api_timeline_entries_update or _partial_update. The agent is left to infer usage entirely from the name.

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