Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api crq quantitative risk hypotheses destroy

ciso_assistant_api_crq_quantitative_risk_hypotheses_destroy
DestructiveIdempotent

Delete a quantitative risk hypothesis by ID to remove outdated or invalid risk scenarios; explicit confirmation helps prevent accidental data loss.

Instructions

api_crq_quantitative_risk_hypotheses_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_hypotheses_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

C2/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 known without the description. The description adds nothing beyond that — no statement of whether deletion is permanent, whether dependent hypothesis data or simulations are cascaded, or whether the operation is soft-delete.

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 a single bare identifier with no wasteful words, but this is under-specification rather than conciseness. There is no front-loaded statement of action, scope, or effect for an agent to anchor on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive delete operation with no output schema, the description should at minimum state what record is removed and whether the deletion is permanent or cascades to related quantitative risk data. Rich annotations partially cover the risk profile, but the definition remains inadequate for an irreversible write tool in a large sibling set of near-identical destroy endpoints.

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 50%: the 'confirm' parameter is well documented in the schema (explicit opt-in for destructive calls when no prompt can be shown), while 'id' is undocumented but self-evident as the target identifier. The description adds zero meaning beyond the schema, so it fails to compensate for 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 the tool name repeated verbatim ('api_crq_quantitative_risk_hypotheses_destroy'), which is a tautology. The name alone lets an agent infer the verb (destroy) and resource (CRQ quantitative risk hypotheses), but the description contributes no additional specificity and does not distinguish it from the sibling partial_update, update, or retrieve tools on the same resource.

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 mention of prerequisites, and no routing to alternatives such as deactivating or updating a hypothesis instead. The only implicit cue is the word 'destroy' in the identifier, which the description merely restates.

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