Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api crq quantitative risk scenarios destroy

ciso_assistant_api_crq_quantitative_risk_scenarios_destroy
DestructiveIdempotent

Deletes a quantitative risk scenario by its ID, requiring explicit confirmation for this destructive action. Use it to remove obsolete or incorrect CRQ scenarios.

Instructions

api_crq_quantitative_risk_scenarios_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_crq_quantitative_risk_scenarios_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, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing on top: it does not say whether deletion cascades to linked hypotheses or studies, whether it is recoverable, or what permissions are needed. No contradiction with annotations, but no added value 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?

It is a single token string with no wasted words, but that is brevity through absence of content rather than conciseness. There is no front-loaded statement of action or consequence to orient the reader.

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 a destructive, non-recoverable-class operation with no output schema and no annotations explaining scope of impact, yet the description offers zero context about what is deleted or what happens to dependent CRQ data. For a tool of this risk profile the definition is functionally empty.

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 'id' parameter has no description at all – and the description supplies no clarification of what identifier is expected or how 'confirm' interacts with clients that can answer prompts. The one documented parameter's own schema text does all the explanatory work.

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's own snake_case name repeated verbatim, which is a tautology rather than a statement of purpose. 'Destroy' does imply deletion of a quantitative risk scenario, but nothing beyond the identifier is conveyed, and the many sibling *_destroy tools mean the name alone carries all the distinguishing work.

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 when-to-use guidance, no mention of alternatives such as partial_update or update for the same CRQ scenario resource, and no stated conditions or prerequisites. An agent learns nothing about when permanent removal is appropriate versus modifying the record.

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