Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api pmbok responsibility matrix activities destroy

ciso_assistant_api_pmbok_responsibility_matrix_activities_destroy
DestructiveIdempotent

Deletes a PMBOK responsibility matrix activity by ID, with an optional confirmation flag for destructive operations.

Instructions

api_pmbok_responsibility_matrix_activities_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_activities_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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether deletion is a hard delete, whether child assignments or matrix cells are removed with it (relevant given the cascade_info sibling), or whether elevated permissions are required.

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 single token is technically brief but is under-specification rather than conciseness; there is no front-loaded verb-object statement, no scope, and no useful structure. Nothing in it earns its place because it merely echoes the name.

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-sounding delete endpoint with an undocumented required id and a confirmation flag, the description carries none of the needed context and no output schema exists to fill the gap. An agent cannot determine the deletion's blast radius or the meaning of confirm from this definition.

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, but `id` has no description, and the tool description supplies no clarification of what identifier is expected (activity UUID vs. matrix-scoped id) or what confirm implies. The description does not compensate for the coverage gap at all.

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 literally the snake_case tool name repeated, so any meaning (destroy = delete a PMBOK responsibility matrix activity) comes from parsing the identifier, not from prose. It does not distinguish this tool from the many sibling *_destroy endpoints or from the activity list/retrieve/update siblings.

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 when-to-use guidance, no statement of prerequisites, and no mention of alternatives such as partial_update or cascade_info_retrieve. An agent is left to infer from the name that this is the deletion path for a responsibility-matrix activity.

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