Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology custom metric samples destroy

ciso_assistant_api_metrology_custom_metric_samples_destroy
DestructiveIdempotent

Deletes a custom metric sample from CISO Assistant metrology by ID, with optional confirmation for destructive operations. Use it to remove obsolete or incorrect sample records.

Instructions

api_metrology_custom_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_custom_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

D1.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, but the description adds zero context on top of that: it does not say what is irreversibly removed, whether related samples or aggregates are affected, or what confirmation behavior to expect. The burden is entirely on structured fields.

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 a single token with no wasted words, but this is under-specification rather than conciseness. There is no front-loaded statement of action or consequence.

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?

A destructive, non-read-only tool with an undocumented id parameter and no output schema requires far more disclosure than a bare name. An agent cannot judge impact, permissions, or side effects before invoking it.

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

Parameters1/5

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

With only 50% schema description coverage, the undocumented 'id' parameter (which sample identifier, what format, from list/retrieve?) needs explanation from the description, and it gets none. The 'confirm' parameter carries its own schema description, so the description contributes nothing to parameter meaning.

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 tool name repeated verbatim ('api_metrology_custom_metric_samples_destroy'), so it is a tautology rather than an explanation. An agent can infer 'destroy a custom metric sample' from the identifier, but the description itself adds no verb-plus-resource statement or scope detail.

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 when-to-use guidance, no prerequisite or permission note, and no mention of when to prefer a sibling such as custom_metric_samples_partial_update or the batch_action variant. Nothing helps an agent choose this tool over the many other *_destroy tools in the sibling list.

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