Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api pmbok responsibility matrices destroy

ciso_assistant_api_pmbok_responsibility_matrices_destroy
DestructiveIdempotent

Deletes a PMBOK responsibility matrix by ID, requiring explicit confirmation for the destructive operation.

Instructions

api_pmbok_responsibility_matrices_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_matrices_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 and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that – it does not say what gets removed (matrix cells, assignments, linked actors/activities), whether deletion is permanent or reversible, or what permissions are required. No contradiction with annotations, but no value added either.

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 that is under-specification, not conciseness – it is a single identifier string with no sentence structure, no front-loaded purpose statement, and no information an agent could act on.

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, non-idempotent-in-spirit delete on a complex PMBOK resource, with only 50% schema coverage and no output schema, the description contains zero explanatory content. An agent cannot tell what is destroyed, what collateral records are affected, or how to confirm safely.

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%: the 'confirm' parameter is documented in the schema, but 'id' has no description and the description text explains neither parameter. It does not clarify what object 'id' identifies (matrix vs. activity vs. actor) or when the confirm flag is genuinely required, leaving the coverage gap uncompensated.

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 nothing but the operation slug "api_pmbok_responsibility_matrices_destroy" – a restatement of the tool name and title. It does convey that a PMBOK responsibility-matrix resource is being destroyed, but adds no verb-level explanation, no scope, and no differentiation from the other *_destroy siblings (e.g. responsibility_matrix_activities_destroy, responsibility_matrix_actors_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?

No guidance whatsoever about when to delete a responsibility matrix, what prerequisites exist, what cascades, or when a sibling delete tool would be the right choice. The agent must infer everything 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