Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_design_releases

Read-only

List signed releases for a design, with an option to include retired or yanked releases kept for audit records.

Instructions

List signed releases for a design.

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": {
      "design_id": "<design_id>"
    },
    "name": "list_design_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYesTarget design.
include_retiredNoInclude yanked releases (records preserved for audit). Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"Target design."
    • changedInput schema / properties / include_retired / description
      Previous value: -"Default: false."New value: +"Include yanked releases (records preserved for audit). Default: false."
  2. Addedv1.5.0

TDQS

B3.2/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 adds the genuinely useful Kiln Pro gating requirement, which annotations cannot express. It says nothing about ordering, result limits, or what a "signed" release record contains beyond the schema's note on retired/yanked entries.

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 lines, front-loaded with the action and followed by the gating requirement; nothing is wasted. The second sentence is a fragment rather than prose, but it carries real information an agent needs.

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 two-parameter read-only list tool with full schema coverage and annotations, the definition covers the essentials plus the plan prerequisite. It stops short of describing the return shape (no output schema exists) or pagination behavior, which leaves minor gaps for an agent deciding what to expect.

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%, including the non-obvious include_retired flag explaining yanked records, so the schema does the heavy lifting. The description adds only that results are limited to signed releases, which is marginal extra meaning over the structured fields. 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?

"List signed releases for a design" is a specific verb plus resource, and "signed" narrows it to a particular release type. It does not name the many similar siblings (list_design_versions, list_feature_releases, cloud_list_remote_releases), so an agent must infer the distinction, but the action itself is unambiguous.

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?

"Needs Kiln Pro" states a prerequisite, which is useful, but there is no guidance on when to pick this over list_design_versions, list_design_branches, or verify_design_release. The agent is left to infer selection criteria entirely.

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