Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api pmbok accreditations destroy

ciso_assistant_api_pmbok_accreditations_destroy
DestructiveIdempotent

Deletes a PMBOK accreditation by ID in CISO Assistant, requiring confirmation when the client cannot handle the destructive-action prompt.

Instructions

api_pmbok_accreditations_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_accreditations_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 from structured data. The description contributes nothing beyond that: it does not say what cascades are deleted, whether the record must be unreferenced, or what permissions are needed, which matters for an irreversible 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 as short as possible with zero waste, but this is under-specification rather than conciseness — a single identifier token that carries no information an agent could not already derive from 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, open-world mutation tool with no output schema and a partially undocumented schema, the description omits everything an agent needs: what is deleted, side effects on related PMBOK objects, and confirmation behavior beyond the schema's own note.

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 only 50%: the 'confirm' flag is documented in the schema, but 'id' has no description and the description text does not explain that it is the accreditation identifier or its format. The description therefore compensates for none of the coverage 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 simply the tool name snake-cased ('api_pmbok_accreditations_destroy'), a tautology that restates the title. It conveys that a PMBOK accreditation is destroyed but adds no scope, no object semantics, and nothing distinguishing it from the numerous sibling destroy tools.

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 at all on when to use this versus ciso_assistant_api_pmbok_accreditations_update, partial_update, cascade_info_retrieve, or the list/retrieve siblings. No prerequisites, no warnings about checking dependencies before deletion.

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