Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology dashboard widgets destroy

ciso_assistant_api_metrology_dashboard_widgets_destroy
DestructiveIdempotent

Deletes a metrology dashboard widget by ID, with explicit confirmation available for clients that cannot answer a prompt.

Instructions

api_metrology_dashboard_widgets_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_metrology_dashboard_widgets_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 at all beyond that – no statement of what is deleted, whether child widgets or dashboard layout are affected, or what authorization is needed. No contradiction with annotations, but zero added value.

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 short, but that is under-specification rather than conciseness – the single token is a machine identifier, not a front-loaded explanatory sentence. Nothing in it earns informational value.

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 mutation with an undocumented required identifier and no output schema, the description provides none of the context an agent needs (what record the id refers to, irreversibility, side effects). The definition is effectively empty beyond the structured fields.

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 documented in the schema, but 'id' has no description anywhere. The description does not clarify that 'id' is the widget identifier (as opposed to a dashboard id), which is exactly the ambiguity an agent needs resolved for this endpoint given the many sibling destroy operations.

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 operation identifier repeated back, so it only restates the name/title rather than stating in prose what the tool does. An agent can infer 'destroy a metrology dashboard widget' from the path segments, but there is no sentence-level explanation and no differentiation from sibling destroy tools such as metrology_dashboards_destroy or metrology_dashboard_widgets_partial_update.

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 on when to use this tool, when not to, or which alternative to prefer for removing or modifying a widget. The agent is left to infer everything from the identifier and the destructive annotation.

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