Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology metric instances destroy

ciso_assistant_api_metrology_metric_instances_destroy
DestructiveIdempotent

Deletes a metrology metric instance by ID, with an optional confirmation flag for destructive API operations.

Instructions

api_metrology_metric_instances_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_instances_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 and openWorldHint=true, so the core risk profile is covered structurally. The description adds nothing beyond that - no statement of what is irreversibly removed, whether cascading effects exist, or what permissions are required - leaving the annotation-covered bar unmet for a destructive operation.

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 the brevity comes from under-specification rather than economy: the single token conveys no information an agent could not derive from the tool name itself. Nothing is front-loaded because nothing meaningful is stated.

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, open-world delete operation with no output schema and only half the parameters documented, the definition is essentially empty. No return expectations, no failure modes (e.g. missing id, unconfirmed destructive action), and no scope of deletion are provided.

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, but 'id' has no description anywhere. The description does not compensate by clarifying what 'id' identifies (a metric instance vs. a definition vs. a sample) or how the confirm flag interacts with the MCP client's prompting behavior.

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 machine slug 'api_metrology_metric_instances_destroy' restated verbatim, which is a tautology of the name. While 'destroy' implies deletion of a metrology metric instance, no natural-language statement of what is deleted or which object type it belongs to is given, and nothing distinguishes it from the many sibling destroy tools (metric_definitions_destroy, custom_metric_samples_destroy, dashboards_destroy).

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 versus alternatives, no prerequisites, and no mention of when not to use it. An agent gets nothing about selecting it over sibling destroy endpoints or over the update/partial_update variants of metric instances.

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