Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology builtin metric samples destroy

ciso_assistant_api_metrology_builtin_metric_samples_destroy
DestructiveIdempotent

Delete a built-in metric sample by ID from CISO Assistant metrology; requires explicit confirmation for this destructive operation.

Instructions

api_metrology_builtin_metric_samples_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_builtin_metric_samples_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 covered structurally. The description adds nothing beyond that — it does not explain that the record is permanently removed, whether the deletion cascades to related metric instances, or when the 'confirm' flag is expected, which is exactly the context a destructive tool should supply.

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?

A single duplicated identifier string is technically concise but conveys no information beyond the tool name; there is no structure, no verb-object sentence, and nothing front-loaded that an agent could act 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, open-world operation with two parameters, an undocumented required 'id', no output schema, and dozens of similarly named destroy siblings, the description should at minimum distinguish this resource and warn about irreversible deletion. It does neither, leaving the definition effectively dependent on the annotations alone.

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 description coverage is only 50%, and the undocumented parameter is the required 'id', which the description never clarifies (identifier of a sample record, format, how to obtain it). The 'confirm' parameter is documented in the schema itself, so the description contributes no additional parameter meaning at all.

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 raw operation ID 'api_metrology_builtin_metric_samples_destroy', a verbatim restatement of the name and title. It implies deletion of metrology built-in metric samples, but offers no elaboration on what a 'builtin metric sample' is or how this differs from the sibling metrology_custom_metric_samples_destroy and the many other *_destroy tools.

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?

No when-to-use guidance, no preconditions, no mention of alternatives such as the custom-metric sibling or refresh/create operations. The agent must infer everything from the name token 'destroy'.

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