Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

check_design_regression

Read-only

Compare ordered design version IDs to detect whether a design prints worse than earlier versions and catch regressions before printing. Requires Kiln Pro.

Instructions

Check if the latest version of a design is printing worse.

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_ids": "<version_ids>"
    },
    "name": "check_design_regression"
  }
}

Input Schema

NameRequiredDescriptionDefault
version_idsYesOrdered list of version IDs (oldest first). At minimum, provide the two most recent versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / version_ids / description
      Added value: +"Ordered list of version IDs (oldest first). At minimum, provide the two most recent versions."
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes the non-obvious Kiln Pro entitlement requirement, but says nothing about what the check produces (a verdict, a regression score, which metrics count as 'worse') or how many versions it needs beyond the schema.

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

Conciseness4/5

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

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the entitlement note. The line break between them is slightly awkward but no sentence is wasted.

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

Completeness3/5

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

For a one-parameter read-only check with no output schema, the definition covers purpose and entitlement but leaves the agent guessing at the result shape and interpretation of 'worse'. It is adequate to invoke, not adequate to interpret.

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 version_ids field already documents the oldest-first ordering and the two-version minimum, so the schema carries the full burden. The description adds no additional meaning about ordering, how many versions are useful, or what happens with more than two.

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 outcome: checks whether the latest design version is 'printing worse' than earlier ones, which is a concrete diagnostic purpose. It does not explicitly distinguish itself from nearby siblings like compare_design_versions, diff_design_versions, or get_regression_alerts, so an agent must infer the boundary from the name alone.

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?

The prerequisite 'Needs Kiln Pro' is stated, which is genuinely useful gating information. However, there is no explicit when-to-use guidance or exclusion pointing to alternative tools (e.g. compare_design_versions for a raw diff versus this tool for a quality regression verdict); usage is only implied by the purpose statement.

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