Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_design_versions

Read-only

Retrieve the version history for a design, newest first, to track changes and review past iterations. Read the scope block to confirm which store was read and whether cloud versions are included.

Instructions

List version history for a design, newest first.

        Args:
            design_id: The design whose versions to list.
            limit: Maximum number of versions to return (default 20).

        Returns:
            A list of version records ordered by version number
            descending, plus a ``scope`` block saying which store
            was read and whether the user's cloud-side versions are
            included.  Read ``scope`` before treating ``count`` as
            the design's whole history.

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_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of versions to return (default 20). Default: 20.
design_idYesThe design whose versions to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / design_id / description
      Added value: +"The design whose versions to list."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 20."New value: +"Maximum number of versions to return (default 20). Default: 20."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -20
    • addedInput schema / properties / limit / description
      Added value: +"Default: 20."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real substance beyond them: results come back ordered by version number descending, a scope block reports which store was read and whether cloud-side versions are included, and it warns against treating count as the design's whole history. That last caveat is exactly the kind of behavioral nuance annotations cannot express.

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

Conciseness3/5

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

The opening sentence and the Returns paragraph are well front-loaded and the scope caveat earns its space. However the Args block is pure duplication of a fully documented schema and could be dropped without information loss.

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?

With no output schema, the description must explain the return value, and it does: version records plus a scope block, with guidance on how to interpret count. For a two-parameter read-only listing tool this is close to complete, with only the sibling-routing guidance missing.

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 Args block repeats the schema text nearly verbatim ('The design whose versions to list', 'Maximum number of versions to return (default 20)'), adding no new meaning. Baseline 3 is appropriate since the schema already carries parameter semantics.

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?

The description names a specific verb+resource ('List version history for a design') and adds scope detail with 'newest first', which is enough to distinguish it from siblings like get_design_version or diff_design_versions. It stops short of explicitly naming the neighboring listing tools (list_design_branches, list_design_releases, search_design_versions), so differentiation is inferred 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?

Usage is implied by 'for a design' and the newest-first ordering, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as search_design_versions or get_design_version. An agent must guess which of the many version-related siblings to pick.

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