Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

show_design_lineage

Read-only

Visualize a design's full version history as a Mermaid flowchart, emphasizing outcomes and success rates so you can trace branches, merges, and cherry-picks.

Instructions

Show the full lineage of a design as a Mermaid flowchart TD with outcomes emphasized.

Free door, tiered answer — Free: Branch · merge · cherry-pick · undo, on the designs you keep · Pro: Branch · merge · cherry-pick · undo, on every design · Business: ✓ · Enterprise: ✓.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "show_design_lineage"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifact_idYesThe design_id.
max_commitsNoNewest-N cap (default 50). Default: 50.
annotate_outcomesNoWhen ``True`` (default), every cell carries its per-material success rates. When ``False``, cells show only the version number and its note. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / annotate_outcomes / description
      Previous value: -"Default: true."New value: +"When ``True`` (default), every cell carries its per-material success rates.  When ``False``, cells show only the version number and its note. Default: true."
    • addedInput schema / properties / artifact_id / description
      Added value: +"The design_id."
    • changedInput schema / properties / max_commits / description
      Previous value: -"Default: 50."New value: +"Newest-N cap (default 50). Default: 50."
  2. Addedv1.5.0

TDQS

B3.1/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 output format and plan gating, but does not explain truncation behavior, pagination, or what 'outcomes emphasized' means 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.

Conciseness3/5

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

The first sentence is front-loaded and clear. The second sentence is a confusing tier matrix with symbols that is not tightly tied to invoking the tool and could be trimmed.

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 read-only lineage visualization with no output schema, the description gives the output format but omits how lineage is scoped, how it relates to sibling ancestry tools, and other return details. It is adequate but has clear gaps.

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%, so the schema already documents all three parameters. The description's 'outcomes emphasized' loosely relates to annotate_outcomes but adds no syntax or meaning beyond what the schema provides.

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 ('Show') and resource ('lineage of a design'), plus the output format as a Mermaid flowchart TD. It does not distinguish this from sibling tools such as get_design_ancestry or visualize_branch_tree, so it falls short of a 5.

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?

Provides no when-to-use or when-not guidance and names no alternatives. The tier sentence describes plan availability rather than selection criteria for this tool versus its siblings.

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