Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_regression_alerts

Read-only

List persisted regression alerts from print outcomes so you can spot and review design failures; filter by design or include dismissed alerts. Requires Kiln Pro.

Instructions

List persisted regression alerts emitted by record_print_outcome.

Needs Kiln Pro.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_regression_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax alerts to return (newest first). Default: 20.
design_idNoOptional — filter to a single design.
include_dismissedNoWhen True, returns alerts the user has already acknowledged. Default False. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"Optional — filter to a single design."
    • changedInput schema / properties / include_dismissed / description
      Previous value: -"Default: false."New value: +"When True, returns alerts the user has already acknowledged.  Default False. Default: false."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 20."New value: +"Max alerts to return (newest first). Default: 20."
  2. Addedv1.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds two things they do not: the alerts are persisted (durable across sessions) and the tool requires a Kiln Pro plan. With no output schema, return-value detail is absent, but the tier gate and data provenance are genuine additions.

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 with zero filler; the core purpose is front-loaded and the prerequisite is clearly separated. Nothing could be removed without losing information.

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 zero-required-parameter, read-only listing tool with full schema coverage and annotations, the definition covers purpose, data origin, and the plan prerequisite. Only the shape of returned alert records is unspecified, which matters little since there is no output schema to rely on but the tool is a simple list.

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% — limit (newest-first, default 20), design_id (single-design filter), and include_dismissed (default false) are all documented in the schema itself. The description adds no further meaning about filtering or ordering, so the baseline of 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?

States a specific verb and resource ("List persisted regression alerts") and even names the originating producer (record_print_outcome), which tells an agent where the data comes from. It does not explicitly contrast with sibling tools like check_design_regression or dismiss_regression_alert, so sibling differentiation is left implicit.

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?

"Needs Kiln Pro" is a useful access prerequisite that tells the agent when the tool will fail, which is more than most definitions offer. However, there is no guidance on when to prefer this listing over check_design_regression or when to follow up with dismiss_regression_alert.

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