Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

dismiss_regression_alert

Destructive

Mark a regression alert as dismissed to stop it from surfacing; optionally target a specific baseline comparison. Requires Kiln Pro.

Instructions

Mark a regression alert as dismissed so it stops surfacing.

Needs Kiln Pro.

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": {
      "version_id": "<version_id>"
    },
    "name": "dismiss_regression_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
version_idYesThe current (regressed) version ID.
previous_version_idNoOptional — dismiss only the alert that compared against this specific baseline. When omitted, every alert for ``version_id`` is dismissed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / previous_version_id / description
      Added value: +"Optional — dismiss only the alert that compared against this specific baseline.  When omitted, every alert for ``version_id`` is dismissed."
    • addedInput schema / properties / version_id / description
      Added value: +"The current (regressed) version ID."
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds two useful facts beyond that — the outcome (the alert stops surfacing) and the Kiln Pro requirement — but omits whether the dismissal is reversible or how to restore a dismissed alert.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero redundancy, with the action and its effect front-loaded before the prerequisite. Nothing here could be cut without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with a fully documented schema, annotations, and no output schema, the description covers the essentials including the tier gate. Only the reversibility of dismissal is left unstated.

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

Parameters3/5

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

Schema description coverage is 100%, and the optional previous_version_id field already documents the scoping behavior thoroughly in the schema. The description contributes nothing about the parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb+resource ('Mark a regression alert as dismissed') with the effect stated, so an agent knows exactly what it does. It never names the read-side sibling get_regression_alerts, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'so it stops surfacing' implies the intent (silencing an alert) and 'Needs Kiln Pro' flags a tier prerequisite. Beyond that there is no when-to-use vs when-not guidance and no pointer to get_regression_alerts as the tool to inspect alerts before dismissing them.

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