Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology metric definitions destroy

ciso_assistant_api_metrology_metric_definitions_destroy
DestructiveIdempotent

Deletes a metrology metric definition by ID, with an optional confirmation flag to safeguard destructive deletion.

Instructions

api_metrology_metric_definitions_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_metric_definitions_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.8/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 structurally. The description adds nothing beyond that: no mention of irreversibility, cascading effects, or permission requirements. It does not contradict the annotations, but it contributes zero behavioral context.

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 shortness here is under-specification rather than conciseness – there is nothing to front-load and no structure to speak of. The single fragment is just the identifier string.

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 of a metrology metric definition with a confirmation parameter and no output schema, an agent needs at least the identity of the resource, the effect of deletion, and the confirm semantics. The annotations cover destructiveness, but the description leaves the resource and confirmation behavior unexplained.

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?

Two parameters with only 50% schema description coverage: 'id' has no description anywhere, while 'confirm' is documented in the schema only. The description explains neither what identifier form 'id' expects nor when confirmation is required, 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 literally the tool name converted to snake_case: 'api_metrology_metric_definitions_destroy'. It conveys only that something named metric definitions is destroyed, with no sentence-level statement of what the tool does. This is tautology – a restatement of the name and title, not an explanation.

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 sibling to use instead. Dozens of sibling *_destroy tools and the related metrology *_update/_partial_update/_retrieve tools exist, and nothing tells the agent how to choose between them or what prerequisite state must hold.

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