Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api crq quantitative risk studies destroy

ciso_assistant_api_crq_quantitative_risk_studies_destroy
DestructiveIdempotent

Permanently delete a quantitative risk study by ID and confirm the destructive operation to remove it from CISO Assistant.

Instructions

api_crq_quantitative_risk_studies_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_studies_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.2/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 from structured data. The description adds nothing beyond that — no note on cascade effects, irreversibility, or what happens to nested hypotheses/scenarios. The schema's `confirm` parameter hints at a confirmation flow, but that is schema text, not description.

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 description is a single token identical to the tool name, with no sentence structure or front-loaded explanation. This is under-specification rather than conciseness — there is no substantive content to be concise about.

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 operation on a domain object with related CRQ entities and no output schema, the description should at minimum state what is deleted and any cascade or permission implications. None of that is present; only the annotations and the schema's `confirm` parameter carry any usable signal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% and the one documented parameter (`confirm`) is explained well in the schema itself; the other (`id`) is a self-evident string identifier. The description adds no meaning, but the schema already does most of the work, so the baseline 3 applies.

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 only the snake_case restatement of the tool name ("api_crq_quantitative_risk_studies_destroy"). It conveys no verb or resource beyond what the identifier already encodes, and it does nothing to distinguish this destroy endpoint from the many sibling *_destroy tools or from the CRQ studies update/partial_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 guidance about when to use this destructive endpoint versus partial_update/update, no prerequisite or permission notes, and no warning about conditions under which deletion should be avoided (e.g. studies with linked hypotheses or scenarios). An 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