Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api pmbok responsibility matrix actors destroy

ciso_assistant_api_pmbok_responsibility_matrix_actors_destroy
DestructiveIdempotent

Delete a PMBOK responsibility matrix actor by ID from CISO Assistant, with optional confirmation for destructive changes.

Instructions

api_pmbok_responsibility_matrix_actors_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_pmbok_responsibility_matrix_actors_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.7/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 known without the description. The description contributes nothing beyond them — no statement of what deletion cascades to (e.g. associated responsibility assignments), whether it is reversible, or what permission is required for a destructive operation.

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 fragment, so nothing is wasted, but the brevity is under-specification rather than conciseness. It is not front-loaded with any actionable information because it contains none.

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?

This is an irreversible destructive endpoint with a confirmation parameter and no output schema, which demands the most descriptive text; instead the description offers nothing. For a delete tool in a large sibling set, an agent has no way to confirm it is the right call from the definition 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 coverage is only 50%: 'confirm' is documented in the schema as an explicit destructive-operation confirmation, but 'id' carries no description anywhere. The description provides no indication that 'id' identifies the actor record, nor any hint about the confirm-then-retry flow the parameter was designed for.

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 the tool name echoed back verbatim: 'api_pmbok_responsibility_matrix_actors_destroy'. An agent can reverse-engineer a rough meaning from the identifier (destroy an actor in a PMBOK responsibility matrix), but the description itself states no verb or resource in prose, making it a tautology rather than an explanation.

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 guidance whatsoever on when to use this tool, when not to, or which sibling to prefer. Given the many near-identical siblings (actors_batch_action_create, actors_partial_update, actors_update, actors_list, responsibility_matrices_destroy), routing to this specific destroy endpoint is left entirely to the caller's inference 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